On Tue, Jul 5, 2011 at 10:16 AM, Tudor Girba <tudor@tudorgirba.com> wrote:

Hi,

The issue is this. The first step Metacello does with a configuration is to go through all versions and reify them. If this step fails, the loading stops.

So, even if you only want to load one specific version, Metacello will still try to reify every version in the configuration. If there is any error, the whole process fails. I am arguing that this is not a wanted behavior :).

I didn't know that :)
And do you/Dale know which other problem can appear while reifying versions? I mean...just to be aware of.

Last question....I remember something about a new way to validate configurations, I think it was using the toolbox. Does someone know how can I validate a configuration and get the results?
�

Did I explain it better now?

yes :)
�

Cheers,
Doru

On 5 Jul 2011, at 08:39, Mariano Martinez Peck wrote:

>
>
> On Tue, Jul 5, 2011 at 12:03 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
> Hi,
>
> The Moose build fails because the Fuel configuration is broken. In particular, in baseline15: there was an error because FuelWithProgressBarBenchmarks was not defined anymore, but it was required. So, I simply removed the requirement. Martin, please take a look.
>
>
> Hi Tudor. Such new version was �a new version 1.3 and new baseline 1.5. Even if baseline15 was not correct, I don't understand how that can impact in Moose because you are still using version 1.2. �And if there is impact, then it is not nice.
>
>
> Please pay attention when building a new version in a Metacello configuration because Metacello tries to reify every version in the Configuration, even if that version is not used. I keep on arguing that this is not a good thing, but at the moment we have to pay more attention :).
>
>
> Sorry, I didn't understand this.
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>

--
www.tudorgirba.com

"Speaking louder won't make the point worthier."