Adding a #development version of a Git project in the catalog
Posted by
Damien Cassou-2 on
Sep 21, 2015; 5:31am
URL: https://forum.world.st/Adding-a-development-version-of-a-Git-project-in-the-catalog-tp4851249.html
Hi,
I have a BaselineOfJenkins on github and I would like to add a
ConfigurationOfJenkins in the catalog. For the #stable versio, I wrote:
stable: spec
<symbolicVersion: #'stable'>
spec for: #common version: '1.0.0'
v1_0_0: spec
<version: '1.0.0'>
spec
for: #'common'
do: [
spec
baseline: 'Jenkins'
with: [ spec repository: 'github://DamienCassou/pharo-jenkins:v1.0.0/src' ];
import: 'Jenkins' ]
But I don't know what to do for the #development version. I tried this
but Metacello does not want it:
development: spec
<symbolicVersion: #'development'>
spec
for: #'common'
do: [
spec
baseline: 'Jenkins'
with: [ spec repository: 'github://DamienCassou/pharo-jenkins:master/src' ];
import: 'Jenkins' ]
On
http://blog.yuriy.tymch.uk/2015/07/pharo-and-github-versioning-revision-2.html,
Yuriy talks about a pre-release, but this requires changing the
#development description for each release.
--
Damien Cassou
http://damiencassou.seasidehosting.st"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill