[ https://issues.apache.org/jira/browse/MNG-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149248#comment-16149248 ]
Robert Scholte commented on MNG-6216: ------------------------------------- bq. were you running parallel builds or two maven sessions concurrently? (Perhaps your IDE was downloading POMs concurrently with your maven CLI build?) bq. I am now wondering if there could be some IDE background downloading and not doing in a concurrent safe way IDE (probably Eclipse at that time) open and running Maven via commandline. So yes, there's a chance that 2 processes are trying to do the same thing, but they are somehow appended at the end. bq. The rebased https://builds.apache.org/blue/organizations/jenkins/maven-3.x-jenkinsfile/detail/MNG-6216/5/pipeline which has the plexus update should handle the doubled pom's (though it would be good to find out where they were originating) That's the wrong conclusion. It contains a fix for the AIOOBE when there's a XML process instruction in a large pom file. So we have the same exception, but with different causes. > ArrayIndexOutOfBoundsException when parsing POM > ------------------------------------------------ > > Key: MNG-6216 > URL: https://issues.apache.org/jira/browse/MNG-6216 > Project: Maven > Issue Type: Bug > Affects Versions: 3.5.0 > Reporter: Marc Savy > Fix For: 3.5.1 > > Attachments: log > > > When building apiman https://github.com/apiman/apiman.git on Maven 3.5.0 the > XML parser seems to have some issues parsing the apiman-test-common module. > If you want to reproduce, you can simply use mvn clean install, no profiles > needed. > Log: https://gist.github.com/msavy/a1b4307fb238a543dfd6af426b42d446 > Also attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
