Re: 'version' contains an expression but should be a constant. Better way to add a new version?

2012-01-16 Thread Ron Wheeler
It looks like you are trying to use releases when you want SNAPSHOTS. Releases should come with a warranty and a specification (written or implied). SNAPSHOTS do not. Ron On 15/01/2012 8:00 PM, Jose Vicente Nunez Zuleta wrote: Hello Stephen, mvn versions:set -DnewVersion=0.1 mvn

'version' contains an expression but should be a constant. Better way to add a new version?

2012-01-15 Thread Jose Vicente Nunez Zuleta
Hi, I want to compile and deploy release artifacts on daily basis to my Maven repository, each version different from the other; Ideally I want to setup a property to do this but Maven complains very strongly about it: Macintosh:walker josevnz$ mvn package -Dwalker.version=20120115 [INFO]

Re: 'version' contains an expression but should be a constant. Better way to add a new version?

2012-01-15 Thread Stephen Connolly
here is why this is a bad plan. the pom that gets deployed will not have the property value resolved, so anyone depending on that pom will pick up the dependency as being the string uninterpolated with the ${ } and much hilarity will ensue in your build process. in maven 2.1.0 and/or 2.2.0 an

Re: 'version' contains an expression but should be a constant. Better way to add a new version?

2012-01-15 Thread Jose Vicente Nunez Zuleta
Hello Stephen, mvn versions:set -DnewVersion=0.1 mvn versions:commit Work like a charm, thanks! On Jan 15, 2012, at 12:31 PM, Stephen Connolly wrote: mvn versions:set - To unsubscribe, e-mail: