[ https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342545#comment-342545 ]
Jörg Hohwiller commented on MNG-2971: ------------------------------------- There is great news for this issue: https://svn.codehaus.org/mojo/trunk/sandbox/consumer-maven-plugin Please note that the plugin will move out of sandbox in the future so try mojo instead of sandbox if the link stopped working: https://svn.codehaus.org/mojo/trunk/mojo/consumer-maven-plugin Simply check-out and install this plugin. Then add this to your toplevel POMs build-section: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>consumer-maven-plugin</artifactId> <version>1.0.0-beta-1-SNAPSHOT</version> </plugin> I hope that the plugin will move out of sandbox and be released soon. If you have any feedback please let us know (ideally on MOJOs dev mailing list). > 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 was sent by Atlassian JIRA (v6.1.6#6162)