[jira] Commented: (MNG-2412) global variable filtering of pom.xml for parent and sub module pom.xml files is not working when deploying to a repository.

["Henrik Brautaset Aronsen (JIRA)" <ji...@codehaus.org>]

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

Henrik Brautaset Aronsen commented on MNG-2412:
-----------------------------------------------

The problem is the install plugin.  It doesn't replace $applicationVersion with the real version in the pom files it installs to your maven2 repository.  See MNG-3057.

> global variable filtering of pom.xml for parent and sub module pom.xml files is not working when deploying to a repository.
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-2412
>                 URL: http://jira.codehaus.org/browse/MNG-2412
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Deployment, Inheritance and Interpolation
>    Affects Versions: 2.0.4
>         Environment: Windows XP., JDK 1.5
>            Reporter: Bill Brown
>             Fix For: 2.1
>
>
> Greetings:  
> I have a maven2 project with two sub modules.  I run into an issue when I build and deploy a SNAPSHOT of this project and try to reference one of the modules as a dependency when I build another project.  
> here is the project structure. 
> project
>     module1
>         pom.xml
>     module2
>         pom.xml
>     pom.xml
> The parent pom declares a global property in the properties section:
> <properties>
>     <applicationVersion>1.1.2-SNAPSHOT</applicationVersion>
>   </properties>
> The parent pom declares the project version in the following way:
> <version>${applicationVersion}</version>
> The module poms refrence the parent pom with the parent tags:
> <parent>
>     <groupId>com.gocsc</groupId>
>     <artifactId>sam</artifactId>
>     <version>${applicationVersion}</version>
>   </parent>
> The module poms both declare the project version in the same way:
> <version>${applicationVersion}</version>
> The project deploys the artifacts to the corporate repository without error but the generated poms for each sub module and also the parent module do not resolve the  ${applicationVersion} in all of the locations:  
> The parent pom project version remains the same in the deployed pom.
> <version>${applicationVersion}</version>
> The parent tags in the sub module poms remain the same:
> <parent>
>     <groupId>com.gocsc</groupId>
>     <artifactId>sam</artifactId>
>     <version>${applicationVersion}</version>
>   </parent>
> The only section that gets resolved / filtered is the project version tags of the sub modules.
> <version>1.1.2-20060628.195852-10</version>
> This seems to be what is causing the problem when I use one of the sub modules as dependency in another project and try to build it.  Here is the output: 
> *****************************************
> [INFO] snapshot com.gocsc:sam-common:1.1.2-SNAPSHOT: checking for updates from com.gocsc
> Downloading: file:///\\gatling\maven2\repository/com/gocsc/sam/${applicationVersion}/sam-${applicationVersion}.pom
> [WARNING] Unable to get resource from repository com.gocsc (file:///\\gatling\maven2\repository)
> Downloading: http://repo1.maven.org/maven2/com/gocsc/sam/${applicationVersion}/sam-${applicationVersion}.pom
> [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2)
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId: com.gocsc
> ArtifactId: sam
> Version: ${applicationVersion}
> Reason: Unable to download the artifact from any repository
>   com.gocsc:sam:pom:${applicationVersion}
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2),
>   com.gocsc (file:///\\gatling\maven2\repository)
> *******************************************************************
> Even if I manually modify the repository pom files to use the timstamp version of: 
> <version>1.1.2-20060628.195852-10</version>
> I still get the same error above.  
> Is this the expected behavior of the system?  Is this a bug? 

-- 
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