[
https://issues.apache.org/jira/browse/MNG-6656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915031#comment-16915031
]
Hudson commented on MNG-6656:
-----------------------------
Build failed in Jenkins: Maven TLP » maven » MNG-6656 #7
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6656/7/
> Introduce base for build/consumer pom
> -------------------------------------
>
> Key: MNG-6656
> URL: https://issues.apache.org/jira/browse/MNG-6656
> Project: Maven
> Issue Type: New Feature
> Components: POM
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.7.0-candidate
>
>
> The pom.xml as we know it has reached it limits, but it is quite hard to do
> improvements as long as the local pom (as part of the sources) is exactly the
> same as the file being published.
> For the Maven eco system it is important that the published file will still
> be a model 4.0.0 to ensure other projects can still depend on these artifacts.
> This will be a first step to separate the poms and to make it possible to
> work on model 5.0.0.
> During install/deploy the pom.xml will be adjusted. At first this means
> removing the modules and adjusting the relativePath elements.
> This is done for the following reasons:
> - these elements refer to relative paths on a local system. Once published
> these elements don't have any value anymore.
> - It will give us experience with manipuating files during install/deploy.
> - We can see IDEs and CI servers can handle this and how we can move forward.
> This feature will at first be disabled by default and can be activated with
> the System property maven.experimental.buildconsumer=true
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
