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: https://github.com/rmannibucau* 2013/5/24 Brett Porter <br...@porterclan.net> > 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.version>hardcoded 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 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: https://github.com/rmannibucau* > > > > > > > > 2013/5/24 Hervé BOUTEMY <herve.bout...@free.fr> > > > >> 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 ${xxx}, which could be interpreted before > inheritance > >> But, taken apart the fact that this would require good explanations to > >> make it > >> understanble by end-users, this would be a new feature that would make > pom > >> not > >> really understandable by actual Maven 3 versions, so there is a > >> compatibility > >> issue to take care > >> > >> Regards, > >> > >> Hervé > >> > >> > >> [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-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > -- > Brett Porter > br...@apache.org > http://brettporter.wordpress.com/ > http://au.linkedin.com/in/brettporter > http://twitter.com/brettporter > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
