[
https://issues.apache.org/jira/browse/MNG-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228050#comment-17228050
]
Hudson commented on MNG-6946:
-----------------------------
Build succeeded in Jenkins: Maven » Maven TLP » maven » MNG-6169/MNG-6553 #14
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6169%252FMNG-6553/14/
> Build/consumer incorrectly transforms name of artifactId
> --------------------------------------------------------
>
> Key: MNG-6946
> URL: https://issues.apache.org/jira/browse/MNG-6946
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.7.0
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Critical
>
> While trying to build maven-clean-plugin with Maven 3.7.0-SNAPSHOT, most
> tests called by the maven-invoker-plugins fail.
> It looks like the copy of maven-plugins-34.pom is one of the root causes.
> Comparing the original and this file (assuming transformation) the following
> are expected differences:
> - removed whitespace around the license
> - removed relativePath
> - removed whitespaces after closing root-tag
> The only invalid difference is
> {{<artifactId>maven-plugin-annotations</artifactId>}}
> which became
> {{<artifactId>tions</artifactId>}}
> There are 2 issues:
> - the artifactId is incorrect
> - as this file is not part of the reactor, there's no need to transform the
> file.
> One thing I noticed as well (only happens with build/consumer active):
> {noformat}
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-bytecode-version) @
> maven-clean-plugin ---
> ERROR: 'The entity "oslash" was referenced, but not declared.'
> {noformat}
> Workaround: add -Dmaven.experimental.buildconsumer=false
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
