You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/06/17 21:53:00 UTC

[jira] [Commented] (MNG-6236) maven-metadata-local.xml polluted with whitespaces

    [ https://issues.apache.org/jira/browse/MNG-6236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515232#comment-16515232 ] 

Michael Osipov commented on MNG-6236:
-------------------------------------

Maven local repository system is not designed for concurrent access. Please try this: https://github.com/takari/takari-local-repository

> 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
>            Priority: Major
>         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
(v7.6.3#76005)