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: [email protected]
For additional commands, e-mail: [email protected]
