Stephen Connolly-2 wrote:
>
> 2009/9/24 Jan <[email protected]>:
>> Hi All,
>>
>> I have multimodule project so i defined a root pom which has entry like
>> <project>
>> <modelVersion>4.0.0</modelVersion>
>> <groupId>Admin</groupId>
>> <artifactId>ProjetA</artifactId>
>> <version>${releaseNumber}</version>
>> .....
>> ....
>> <modules>
>> <module>my-modA</module>
>> <module>my-modB</module>
>> <module>my-modC</module>
>> <module>my-modD</module>
>>
>> then in child pom i refer my pom like
>>
>> <project>
>> <modelVersion>4.0.0</modelVersion>
>> <parent>
>> <groupId>Admin</groupId>
>> <artifactId>ProjectA</artifactId>
>> <version>${releaseNumber}</version>
>> <relativePath>${basedir}/../pom.xml</relativePath>
>> </parent>
>>
>>
>> now when i run mvn -DreleaseNumber="55.0.0.0" clean install from the root
>> level everything works fine,
>
> everything working fine is a bug. i.e. property substitution should
> not be allowed in /project/parent/(groupId|artifactId|version) or in
> /project/(groupId|artifactId|version)
>
Could you clarify? Are you against the Application Version concept on this
page:
http://docs.codehaus.org/display/MAVEN/best+practices+-+version+management+in+multi+project+bu
Is this no longer a "best practice"?
Thanks,
Paul
--
View this message in context:
http://www.nabble.com/Pom-Parent-Version-Properties-tp25597937p25671120.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
