Matthew Janssen commented on MNG-6216:

Thanks for the reply [~rfscholte]. That's what's so baffling about this to me. 
I made sure that my system is set up just like his. 
Here is the result of my co-worker's `mvn -version` run: 
Here is the result of my `mvn -version` run: 
The only differences I'm seeing are the installation directories and the java 

As far as your other questions: if I recall correctly my co-worker runs 
commands both from within Eclipse (he's using Mars) and the command line (but I 
think it's from the command line a majority of the time). I, personally, run 
maven commands exclusively from the command line. We don't have any special 
thread configuration so it's just whatever the maven default is which I assume 
is single-threaded. And the OS/Java versions are included in the gists above. 

Some other notes: the `settings.xml` files in our `maven\conf` folder are just 
the standard settings (no changes for either of us) and neither of us have a 
`settings.xml` in our m2 repo either. 
Both of us started from clean m2 repos right after we updated to maven 3.5.0. 
We didn't run maven installs on all of the exact same jars in the exact same 
order but the project we're working on now has us working with the same general 
jars so we had installed similar projects over the same time period. 

For me, this error doesn't occur on every project I try to install, it just 
crops up sometime and then I can never install that project without clearing my 
m2 repo. I've wiped my m2 repo multiple times. After each time, there's a high 
probability that _will_ be able to install the troublesome jar but a different 
jar will inevitably fail at some point.

Let me know if there's any more info I can provide to help get to the bottom of 

> 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

Reply via email to