MetacelloToolBox

Hi!

I just realized that the version creation feature offered by metacello tool box produces odd version.

Sorry for this cut&paste email.
For example, before I use the tool box I had the following versions (which is really what I except):
-=-=-=-=-=-=-=-=-=-=-=-=
version116: spec
        <version: '1.16' imports: #('1.4-baseline')>

        spec for: #common do: [
                spec blessing: #release.
                        spec package: 'Spy' with: 'Spy-AlexandreBergel.241'.
                ].
version117: spec
        <version: '1.17' imports: #('1.4-baseline')>

        spec for: #common do: [
                spec blessing: #release.
                        spec package: 'Spy' with: 'Spy-AlexandreBergel.242'.
                ].
version118: spec
        <version: '1.18' imports: #('1.4-baseline')>

        spec for: #common do: [
                spec blessing: #release.
                        spec package: 'Spy' with: 'Spy-AlexandreBergel.243'.
                ].
-=-=-=-=-=-=-=-=-=-=-=-=

With the toolbox, I have


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
version119: spec
        <version: '1.19' imports: #('1.4-baseline' )>

        spec for: #'common' do: [
                spec blessing: #'development'.
                spec description: 'New version'.
                spec author: 'AlexandreBergel'.
                spec timestamp: '1/24/2011 16:01'.
                spec
                        project: 'MemoryMonitor' ;
                        project: 'Merlin' with: '1.0';
                        project: 'Mondrian' with: '2.42';
                        project: 'HealthReportProducer' with: '1.1'.
                spec package: 'Spy' with: 'Spy-AlexandreBergel.244'.].

version120: spec
        <version: '1.2' imports: #('1.0-baseline') >
       
        spec for: #common do: [
                spec
                        blessing: #unstable;
                        author: 'AlexandreBergel'.

                spec project: 'MemoryMonitor' with: '1.0'.
                spec project: 'Mondrian' with: 'default'.
                spec
                        package: 'Spy' with: 'Spy-AlexandreBergel.165'].

version140: spec
        <version: '1.4' imports: #('1.3-baseline') >
       
        spec for: #common do: [
                spec
                        blessing: #release;
                        author: 'AlexandreBergel'.

                spec project: 'MemoryMonitor' with: '1.0.2'.
                spec project: 'Mondrian' with: 'default'.
                spec
                        package: 'Spy' with: 'Spy-AlexandreBergel.221'].
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

I am not sure how the baseline is picked. Any idea where this comes from?

I use MetacelloBrowser to do an automatically saving...

Cheers,
Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Hey Alexandre,

I'm not sure I understand what the the problem is? Could you highlight
the unexpected values and describe what you expected to see?

Dale

On 01/24/2011 11:12 AM, Alexandre Bergel wrote:

> Hey Alexandre,
>
> I'm not sure I understand what the the problem is? Could you highlight the unexpected values and describe what you expected to see?

My email was half-frenetic. Sorry about that. Before I used ToolBox, I build versions by identifying which packages are used in the last baseline defined in the configuration.

Now, the toolbox does it for me. But in a way that I do not fully understand.
Evaluating "ConfigurationOfSpy project" raises an error "ByteString>>projectSpec not understood". By inspecting the stack I see that version 1.19 is the culprit. I do not really now why. It would be so easy if we could met.

Cheers,
Alexandre


--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Alexandre,

The line:

   project: 'MemoryMonitor' ;

Looks like it would be the cause of the problem ... have you tried
running the validator on the configuration? The validator is supposed to
help you with these kinds of problems and tell you where the problem
might be...

Was version 1.19 produced by the toolbox? The toolbox is supposed to
validate the config after each edit so if the toolbox was used to
produce the version I would have expected an immediate validation error,
if you didn't get a validation error or it wasn't helpful I would like
to know the sequence of commands that you used so I can address the
problem ...

Dale

On 01/24/2011 12:55 PM, Alexandre Bergel wrote:

Sorry for the late reply. I am just back from holidays.

> The line:
>
>  project: 'MemoryMonitor' ;
>
> Looks like it would be the cause of the problem ... have you tried running the validator on the configuration? The validator is supposed to help you with these kinds of problems and tell you where the problem might be...
>
> Was version 1.19 produced by the toolbox? The toolbox is supposed to validate the config after each edit so if the toolbox was used to produce the version I would have expected an immediate validation error, if you didn't get a validation error or it wasn't helpful I would like to know the sequence of commands that you used so I can address the problem ...

Yes, it was produced by the toolbox.
I will go back to MetacelloBrowser since we plan to use it for Moose.

Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.