|
||||||||
|
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/groups/opt_out.
Me too.
The same problem is restricted to job of type Maven2/3. With a job of kind general and a "Maven build" step there is no problem.
Reason is the different handle of Maven execution and its exception in the MavenExecutionResult object. In a job of kind general is demand to Maven executable (Embedded Maven) instead in a job of kind Maven2/3 was reimplemented by jenkins to parse informations about sub-modules.
I propose a solution with this pull request https://github.com/jenkinsci/jenkins/pull/851