[
http://jira.codehaus.org/browse/MINSTALL-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94680
]
Stephane Nicoll commented on MINSTALL-20:
-----------------------------------------
not sure it's related to the install plugin. This sounds like a bad practice to
me.
> Variables are not replaced into installed pom file
> --------------------------------------------------
>
> Key: MINSTALL-20
> URL: http://jira.codehaus.org/browse/MINSTALL-20
> Project: Maven 2.x Install Plugin
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: Windows, Solaris
> Maven version 2.0.4
> Reporter: Laurent Dauvilaire
>
> 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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
