You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Luke Lu (JIRA)" <ji...@codehaus.org> on 2011/04/10 02:32:23 UTC

[jira] Commented: (MNG-2971) Variables are not replaced into installed pom file

    [ http://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263052#action_263052 ] 

Luke Lu commented on MNG-2971:
------------------------------

IMO, the right fix would be to allow "controlled" property expansion of user defined properties via the maven-install-plugin, a la the latest ant filter <expandproperties regex=".*\.version$"/>, as you definitely do NOT want to expand ${java.home} or ${project.build.directory} etc. maven-install-plugin probably should expand anything in <version> elements by default.

Right now, my workaround is to use maven-antrun-plugin to sanitize the poms before install. The maven-assembly-plugin filter workaround would not work for me as it expands all the properties. 

> Variables are not replaced into installed pom file
> --------------------------------------------------
>
>                 Key: MNG-2971
>                 URL: http://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
>
>
> 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