![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
olamy
|
|
Components:
|
maven-dependency-update-trigger |
|
Created:
|
19/Feb/14 11:16 PM
|
|
Description:
|
Consider this scenario:
- Maven project A contains two modules, A1 (a jar) and A2 (a war), both of which declare A as their parent.
- A's POM lists A1 and A2 in the <dependencyManagement> section.
- A2's POM declares a dependency on A1.
- Maven project B contains two modules, B1 (a jar) and B2 (a war), both of which declare B as their parent.
- B's POM lists B1, B2, and A1 in the <dependencyManagement> section.
- B2's POM declares a dependency on A1, but not A2.
The problem:
Jenkins lists A2 as an upstream project of B2, when the build option "Build whenever a SNAPSHOT dependency is built" is checked, which causes B2 to be built when changes are made to A2, but there are no explicit or transitive dependencies between A2 and B2.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Paul Schifferer
|
|
|
|
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.
