maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gustavo Chaves (JIRA)" <>
Subject [jira] (MNG-2971) Variables are not replaced into installed pom file
Date Wed, 14 Mar 2012 19:35:03 GMT


Gustavo Chaves commented on MNG-2971:

Hi. I noticed that MNG-4223, which is already related to this issue, seems to be much more
researched. Strictly speaking it is a restricted version of this, because it cares only about
the artifact coordinate tags with regards to property expansion and not the whole POM. However,
since the description of this issue exemplifies the problem with the <version> tag I
think that probably the artifact coordinates are all this issue's reporter cares about.

Is that so?

If it is, I think it would be a good idea to close this issue marking it as a duplicate of
MNG-4223 in order to focus the efforts towards a solution.

> Variables are not replaced into installed pom file
> --------------------------------------------------
>                 Key: MNG-2971
>                 URL:
>             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=""
>          xmlns:xsi=""
>          xsi:schemaLocation="">
> 	<modelVersion>4.0.0</modelVersion>
> 	<groupId></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:!default.jspa
For more information on JIRA, see:


View raw message