[
https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021097#comment-16021097
]
Michael Osipov edited comment on MNG-6236 at 5/23/17 12:04 PM:
---------------------------------------------------------------
Checked the file: this file can't be the one you are having trouble with. The
parser says that something is after {{</metadata>\n}} but there is nothing in
your file. Please double-check. Alternatively, throw away your local repo and
have it rebuilt.
was (Author: michael-o):
Checked the file: this file can't be the one you are having trouble with. The
parser says that something is after {{</metadata>\n}} but there is nothing in
your file. Please double-check.
> maven-metadata-local.xml polluted with whitespaces
> --------------------------------------------------
>
> Key: MNG-6236
> URL: https://issues.apache.org/jira/browse/MNG-6236
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.5.0
> Reporter: Tomer Cohen
> Attachments: maven-metadata-local.xml, stacktrace.txt
>
>
> After starting to use Maven 3.5.0 multiple instances of the attached
> exceptions started occurring when multiple builds are using and installing
> modules of the same reactor. I sanitized the module name.
> Maven 3.3.9 did not have this issue
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
