[
https://issues.jenkins-ci.org/browse/JENKINS-12735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158910#comment-158910
]
sergei_ivanov commented on JENKINS-12735:
-----------------------------------------
Please add support for automatic resolution of version ranges in Maven
dependencies into upstream and downstream relationships between the
correcponding Jenkins jobs.
We started using version ranges in our project, because we have a very fluid
development environment. We manage almost a hundred of modules, which have
dependencies between themselves, and which are assembled into applications
often with a very short release cycle. Our key requirement is to always keep
all module dependencies in sync, essentially by always depending on the latest
available version. Without version ranges it becomes a royal pain, because
after the release of each module, a newly released module version has to be
propagated into all dependencies. If we were to do that, we'd have spent half
of our time updating dependencies in the projects.
If the changes in the patch have a potential to destabilise Jenkins for the
existing users, let's make this option configurable from either Jenkins
configuration, or individual job configuration.
> No upstream or downstream resolution with Maven version ranges
> --------------------------------------------------------------
>
> Key: JENKINS-12735
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12735
> Project: Jenkins
> Issue Type: Bug
> Components: maven
> Affects Versions: current
> Reporter: Alex Koon
>
> 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?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
