...
As a first step to test consequences of differentiating build from consumer POM, a choice on a few differences has been made:
removal of project.version in build POM: in case the <parent/> is located at its relativePath (default: ../pom.xml), the version can be removed from build POM. groupId and artifactId are still required to ensure it is being matched with the right parent.Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key MNG-624 removal of dependencies versions in build POM: dependencies that are part of the reactor don't need a version anymore
cifriendly placeholders in versions (${sha1}, ${revision}, ${changelist}) in build POM will be resolved in consumer POM
<modules> from <project> will be removed from consumer POM
<relativePath> from <parent> will be removed from consumer POM
...