[Moose-dev] Re: Blueprint migrated into Roassal

Ok. I took a quick look. There are multiple problems. First, there are two branches in the repository (one from Alex, one from Jura). There is even a branch in the Configuration package. This is why I say that working only at the level of Metacello is problematic when you have more than one (actually in this case the configuration package was branched by Alex alone :)) developers because the tools leave you blind to such situations. Another problem comes from the ConfigurationOfRoassal: #development points to an old version, and this is why the Roassal job succeeds. In the meantime, the Moose job shows that the Blueprint visualizations are broken because of the missing extensions to ROMondrianViewBuilder. This aside, after loading and merging manually the code in the Moose image everything worked fine. In the meantime, I merged the packages Roassal package. I also committed a new configuration in which development points to 0.5-baseline for now. Just, please note that there are two configuration versions that are not part of the branch. I think the only difference is that stable should point to 1.331. Alex, could you check? Cheers, Doru On Apr 24, 2013, at 9:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: -- www.tudorgirba.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."