Thank you Robert! I *knew* it was something core :-) Expand this syntax *everywhere* and allow people more control over what happens? Seems like a solid solution at face value, but could have gotchas, of course...
On Fri, May 24, 2013 at 7:46 PM, Robert Scholte <rfscho...@apache.org>wrote: > http://maven.apache.org/maven-**release/maven-release-plugin/** > prepare-mojo.html#**tagNameFormat<http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#tagNameFormat>uses > @{} so it is not resolved immediately, but only when the plugin wants > to. > > maven-invoker-plugin only filters @value@ when cloning projects to the > target, so the ${value} are only resolved during execution. > > Robert > > > Op Fri, 24 May 2013 18:59:20 +0200 schreef Fred Cooke < > fred.co...@gmail.com>: > > > Definitely not that, I've not used it, however something else does have a >> @{} syntax, something common. I'm sorry that I can't recall right now >> what >> it was. >> >> On Fri, May 24, 2013 at 6:54 PM, Hervé BOUTEMY <herve.bout...@free.fr >> >wrote: >> >> maven-invoker-plugin filtering? >>> >>> http://maven.apache.org/**plugins/maven-invoker-plugin/** >>> examples/filtering.html<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/<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<dev-unsubscr...@maven.apache.org> >>> > > For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> ------------------------------**------------------------------** >>> --------- >>> To unsubscribe, e-mail: >>> dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org> >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org> > For additional commands, e-mail: dev-h...@maven.apache.org > >
