yes, it is the expected behaviour
see [1] for complete documentation of the model building algorithm:
project.version is evaluated during model interpolation, which happens after
inheritance
AFAIK, there is no feature to evaluate before inheritance: this would require
a new notation than
Yes, that's what i expected but ATM in TomEE we have
openejb.versionhardcoded version/ and for half of the project it
matches the project.version (but only half :().
That's not blocking at all but if maven could get this kind of feature
(maybe #{project.version}) it would be really great
*Romain
You're project will need to be aware of its own structure, but you can use
things like this: ${project.parent.version}
- Brett
On 23/05/2013, at 11:20 PM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
Yes, that's what i expected but ATM in TomEE we have
openejb.versionhardcoded version/
that's not possible, we use it in too much place and our project is not flat
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github:
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?)
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
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.frwrote:
maven-invoker-plugin filtering?
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
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.orgwrote:
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
10 matches
Mail list logo
