search

sampig / spock

Automatically exported from code.google.com/p/spock
0 stars 0 forks source link

0.5-groovy-1.8 release contains dependency on SNAPSHOT (groovy-all) ? #180

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem? If possible, provide source code and
stack trace.
1. mvn install
2. Freak out --->>> wants a SNAPSHOT (groovy-all)
3. Resolve using codehaus snapshot repo

Original issue reported on code.google.com by pino.silvaggio on 9 May 2011 at 6:32

GoogleCodeExporter commented 9 years ago 
0.5-groovy-1.8 was based on the latest prerelease version of Groovy at that 
time and is outdated by now. There is no Spock release for Groovy 1.8 final 
yet, but you can use 0.6-groovy-1.8-SNAPSHOT if you wish.

Original comment by pnied...@gmail.com on 9 May 2011 at 6:42

GoogleCodeExporter commented 9 years ago 
Ok, fair.

However, it would be a good idea to avoid releasing (tagging) a project that 
contains SNAPSHOT dependencies.

One way to resolve this problem is to simply build a SNAPSHOT release of the 
dependency in question. Example, rebuild and deploy groovy-all changing the 
version to something like 1.8.0-beta3-201109030001 or 
1.8.0-beta3-r{SVN_REVISION}... Deploy in your repository... Not doing so will 
eventually break your build since the SNAPSHOTs will be removed once it is 
released.

The other solution is to use dependency version ranges.

Thanks, keep up the good work your framework is great.

Original comment by pino.silvaggio on 9 May 2011 at 7:28