|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

I was unable to reproduce this with 1.598 on CentOS with OpenJDK 1.7, building on the master node, using a fresh Jenkins home only installing Git plugin.
I tried with the Jenkins project at https://github.com/jenkinsci/jenkins and always got past the Parsing POMs state with both Maven Project plugin 1.1 and 1.2.
Could someone please try to reproduce this issue using a pristine Jenkins home directory (as easy as