Is there a Maven-way to do continuous delivery then? As opposed
to continuous integration.
Our current hack is to use the date as the maintenance version as a
variable for example 3.1.20160102
G
On Mon, Mar 7, 2016 at 11:18 AM, Eric B <ebenza...@gmail.com> wrote:
> I personally have a pet-peeve of using system variables to define version
> numbers; I find it is counter productive to the building of maven
> artifacts. There is no traceability to determine the actual version of an
> artifact once it has been built. At least having a fixed version number in
> the <version> element shows up in the META-INF/maven/../pom.* files.
>
> Is using a variable for the version even a good idea?
>
> Thanks,
>
> Eric
>
>
> On Mon, Mar 7, 2016 at 4:04 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > only specific properties are permitted for expansion in XPath paths that
> > match the following regex /project/(parent/)?(groupId|artifactId|version)
> >
> > On 2 March 2016 at 05:39, Raghu <raghunath...@yahoo.com.invalid> wrote:
> >
> > > I have a POM with parent node as below: <parent>
> > > <groupId>com.test</groupId> <artifactId>pom.parent</artifactId>
> > > <version>${test.version}</version>
> > > <relativePath>../scripts/pom.xml</relativePath> </parent>
> > > This used to work till maven 3.3.3 version - mvn clean install.
> However,
> > > the version 3.3.9 throws error though. When I change the version to a
> > value
> > > instead of the variable, it works fine.
> > > Won't maven support variable for version? Or is it a bug with 3.3.9?
> > > Appreciate your response...
> > > - regards,raghu
> >
>
--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
