![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Jesse Glick
|
|
Components:
|
maven |
|
Created:
|
29/Apr/13 2:52 PM
|
|
Description:
|
If custom settings.xml are used for a job in such a way that parent POMs are not accessible without considering the full environment of model building (details TBD), it can happen that the Maven build itself succeeds yet MavenFingerprinter.recordParents fails to find parent POMs and so aborts the build. The root problem is the use of MavenProject.getParent, which is very problematic and in fact can throw an undocumented exception as MNG-5075 notes.
Any such exception should be caught, perhaps logged, and fingerprinting should proceed.
Further, the model should be computed in such a way that the parent can be resolved to begin with. This may mean dropping usages of getParent.
|
|
Environment:
|
1.459
|
|
Project:
|
Jenkins
|
|
Labels:
|
exception
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Jesse Glick
|
|
|
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
