maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Connolly (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5358) Install Plugin installs poms that contain variables in artifact version and parent version
Date Mon, 15 Oct 2012 14:37:36 GMT

     [ https://jira.codehaus.org/browse/MNG-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stephen Connolly closed MNG-5358.
---------------------------------

    Resolution: Not A Bug

Property substitution is not supported at the following XPath locations

/project/parent/groupId
/project/parent/artifactId
/project/parent/version
/project/groupId
/project/artifactId
/project/version
/project/packaging

Doe in part to Maven Core currently requiring that the unresolved POM be deployed to the remote
repository (or else inheritance fails) and when used as a dependency the properties supplied
at original build time will not be available to the depending project.

One attempt at solving this issue was to resolve the properties in the pom before installing/deploying
but that broke a bunch of projects that relied on overriding properties to control the version
specified in <dependencyManagement> among other things. This one of the reasons why
Maven 2.1.0 and 2.2.0 are not recommended for use.
                
> Install Plugin installs poms that contain variables in artifact version and parent version
> ------------------------------------------------------------------------------------------
>
>                 Key: MNG-5358
>                 URL: https://jira.codehaus.org/browse/MNG-5358
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories, Deployment
>    Affects Versions: 3.0.3
>            Reporter: Christofer Dutz
>         Attachments: module1-1.2-SNAPSHOT.pom, module2-1.2-SNAPSHOT.pom, TestProject-1.2-SNAPSHOT.pom,
Test.zip
>
>
> I am currently trying to create a build process that is optimized for being able to have
individual modules of one project deployed with different versions. Therefore I created a
build that uses properties for providing the version numbers for artifacts, dependencies and
parent relations. The build is working nicely, unfortunately the install plugin installs the
artifacts into the correct directories, but it doesn't replace the properties. This way the
repo contains artifacts it can certainly not resolve ich a user checks out only part of the
project.
> I created a small test-project. If you simply "mvn install" it you will see the problematic
results.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message