[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305891#comment-305891
]
Mike Gould commented on MNG-2971:
---------------------------------
We need this for a multi-module build. We want to specify that some sibling
module dependencies have the same version as the parent or current project. If
we do this:
<dependency>
<groupId>com.example</groupId>
<artifactId>common</artifactId>
<version>${project.version}</version>
<scope>compile</scope>
</dependency>
then the varible appears in the installed pom and then can't be used by
anything.
Currently - like most people - we have a pre-build step which sets all versions
accross the whole tree.
Putting this functionality into the release plugin would be completely useless
as the release plugin simply doesn't do the right thing for CI style builds
where the version is set from the build number/scm revision etc.
> Variables are not replaced into installed pom file
> --------------------------------------------------
>
> Key: MNG-2971
> URL: https://jira.codehaus.org/browse/MNG-2971
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Deployment, Inheritance and Interpolation
> Environment: Windows, Solaris
> Maven version 2.0.4
> Reporter: Laurent Dauvilaire
> Assignee: Ralph Goers
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: pom.xml
>
>
> Variables are not replaced into installed pom file.
> Here is a sample pom file
> <project xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.xxx.root</groupId>
> <artifactId>root</artifactId>
> <packaging>pom</packaging>
> <version>${prop.version}</version>
> <name>My Project</name>
> ...
> <properties>
> <prop.version>3.0.20</prop.version>
> </properties>
> </project>
> The installed pom is into
> ${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
> is the same as the project pom file but the version referenced into the
> installed pom file is ${prop.version} instead of 3.0.20
> which creates problem to artifacts depending of this one.
> Thanks in advance
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
