> On 09/21/2015 10:46 AM, Dale Henrichs wrote:
>>
>>
>> On 09/21/2015 06:31 AM, Damien Cassou wrote:
>>> Yuriy Tymchuk <[hidden email]> writes:
>>>
>>>> Can you simply define symbolic version as a normal one?
>>>
>>> when I tried I got an error message. Metacello was trying to parse
>>> 'development' as a semantic version number
>> You can implement #versionNumberClass in your configuration or
>> baseline to switch version number parser to MetacelloVersionNumber
>> which is less picky:)
>>
>>   versionNumberClass
>>     ^ MetacelloVersionNumber
> So using MetacelloVersionNumber does look like you can define the
> following version:
>
> versionDev: spec
>    <version: 'dev'>
>    spec
>      for: #'common'
>      do: [
>        spec
>          baseline: 'Jenkins'
>            with: [ spec repository:
> 'github://DamienCassou/pharo-jenkins:master/src' ];
>          import: 'Jenkins' ]
>
> and then use a standard symbolic version definition:
>
> development: spec
>    <symbolicVersion: #'development'>
>    spec for: #'common' version: 'dev'