[
https://issues.apache.org/jira/browse/MNG-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117364#comment-16117364
]
Matthew Janssen commented on MNG-6216:
--------------------------------------
I'm adding a comment to vote for a fix for this. I've been running into this
non-stop on my machine after upgrading to maven 3.5.0. My coworker hasn't
encountered this at all. Right now, it appears that the only way around it is
to wipe the entire .m2 repo? That works for me but I don't want to have to do
that every week. I was able to find some 'corrupted' poms in my repo (where the
entire <project></project> structure was duplicated. I deleted those poms but I
still got the same failure on my project. So I'm not sure exactly what's going
on. But maybe a new maven release/fix would solve my problems. Just hoping this
can come sooner than later as it's really slowing down my development.
> 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)
