[
http://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176673#action_176673
]
Jörg Hohwiller commented on MNG-2971:
-------------------------------------
Good point, Gavin. I also voted for this issue, but you are right. It might be
a bad idea to let maven figure out what you want by some magic. But if the
variable is NOT defined in the POM itself (including inheritance from parent
POMs) then it cant be wrong to replace the
variable because otherwise the installed POM is bad.
Another way to solve this properly is maybe some command line option to
activate this feature. But then you still would not have both ways at a time.
An additional tag in <dependency> as trigger, that is stripped when installed,
is also a possibility.
I also opened MNG-4161 so maybe that is a different solution that mainly
addresses the same problem if someone cares or wants to vote for.
> Variables are not replaced into installed pom file
> --------------------------------------------------
>
> Key: MNG-2971
> URL: http://jira.codehaus.org/browse/MNG-2971
> Project: Maven 2
> Issue Type: Bug
> Components: Deployment, Inheritance and Interpolation
> Environment: Windows, Solaris
> Maven version 2.0.4
> Reporter: Laurent Dauvilaire
> Assignee: Ralph Goers
> Fix For: 2.2.x
>
>
> 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
