[
https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025114#comment-16025114
]
Michael Osipov commented on MNG-6236:
-------------------------------------
Got it, this is one seriously broken. It is not polluted with whitespace but
really really broken:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<metadata modelVersion="1.1.0">
<groupId>BLABLA</groupId>
<artifactId>BLABLA</artifactId>
<version>18.0-SNAPSHOT</version>
<versioning>
<snapshot>
<localCopy>true</localCopy>
</snapshot>
<lastUpdated>20170525173245</lastUpdated>
<snapshotVersions>
<snapshotVersion>
<extension>jar</extension>
<value>18.0-SNAPSHOT</value>
<updated>20170525173245</updated>
</snapshotVersion>
<snapshotVersion>
<extension>pom</extension>
<value>18.0-SNAPSHOT</value>
<updated>20170525173245</updated>
</snapshotVersion>
</snapshotVersions>
</versioning>
</metadata>
/classifier>
<extension>jar</extension>
<value>18.0-SNAPSHOT</value>
<updated>20170525173240</updated>
</snapshotVersion>
</snapshotVersions>
</versioning>
</metadata>
{code}
Can you anyhow provide a way to reproduce it otherwise I won't be even able to
take a look at the cause.
> 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)
