maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <herve.bout...@free.fr>
Subject Re: Project.version too contextual
Date Fri, 24 May 2013 16:54:57 GMT
maven-invoker-plugin filtering?
http://maven.apache.org/plugins/maven-invoker-plugin/examples/filtering.html

Le vendredi 24 mai 2013 13:01:08 Fred Cooke a écrit :
> > AFAIK, there is no feature to evaluate before inheritance: this would
> > require
> 
> a new notation than ${xxx}, which could be interpreted before inheritance
> 
> 
> If I recall correctly, and I still need to apologise to you for my last
> mistake, there is something like @{} in use in one of the (core?) plugins?
> I seem to remember trying to use it elsewhere and being disappointed :-)
> 
> Regards,
> 
> Fred.
> 
> [1] http://maven.apache.org/ref/3.1.0-alpha-1/maven-model-builder/
> 
> > Le vendredi 24 mai 2013 06:43:35 Romain Manni-Bucau a écrit :
> > > Hi guys,
> > > 
> > > Project.version seems evaluated by pom and not from the pom it is
> > > defined
> > > (at least in a multi modules project without a single version).
> > > 
> > > So basically you can get a version very different from the expected one.
> > > 
> > > If this is the expected behavior, could it be another variable to force
> > 
> > the
> > 
> > > origin version?
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message