[
https://jira.codehaus.org/browse/MNG-5358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311511#comment-311511
]
Christofer Dutz commented on MNG-5358:
--------------------------------------
You state that resolving the parent pom would break inheritance, but not
resolving it certainly breaks it the way it currently works.
> 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
