|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-15237) Dependent Maven Jobs igno... [email protected] (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... [email protected] (JIRA)
- [JIRA] (JENKINS-15237) Dependent Maven Jobs... [email protected] (JIRA)

I can confirm the problem too (jenkins 1.483)
It seems that not only the SNAPSHOT version is ignored. I see a project (which depends on a release version dependency!) build triggert by a upstream build of the completely unrelated SNAPSHOT version of that dependency. Therefore our complete jenkins build server kept busy by building unrelated projects. Very annoying!