Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
This is essentially reopening JENKINS-2787 (https://issues.jenkins-ci.org/browse/JENKINS-2787). We are in an environment where we do have version ranges and ignoring the arguments for or against version ranges, we like to resolve this issue. I have looked at the patch provided in JENKINS-2787 and have integrated this into the latest 1.450 of jenkins and running this in our CI environment.
What would be required to submit this latest patch to Jenkins and have this promoted?
Attachments
Issue Links
- duplicates
-
JENKINS-2787 Hudson doesn't support Maven2 dependency version ranges
-
- Resolved
-
- is related to
-
JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven
-
- Closed
-
This could be the reason, I remember there was some breaking change from 3.0.3 to 3.0.4 with SNAPSHOTS in version ranges, but i can't find it anymore.
But, there's still MNG-3092 , which could be the main reason behind it. This thread on the maven list also goes in detail about the problem.