[
http://jira.codehaus.org/browse/MVERSIONS-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216318#action_216318
]
Erik Schepers commented on MVERSIONS-102:
-----------------------------------------
I'm not sure if anyone would use this plugin if they have unresolvable
dependencies (being them transitive or direct). If so, than this patch imposes
a problem indeed, and it maybe better to create a separate goal.
However, if you make it a new goal, than the plugin has two goals, that do
almost the same.
It would be better to try to resolve the dependencies only when the
transitive-flag is true. However, I don't know how to do that (I've tried, but
the only way I can get it to work is by adding the
@requiresDependencyResolution tag... If you have any hints or ideas, I'm
willing to spend some more effort on it.
On the other issue, yes you're right that upgrading transitives could break
things, but with this feature I'm not upgrading, but only getting the
notification of a newer version.
Our usecase for this feature is that we use it during the release of our
products. Typically, we want to use the latest versions of all dependencies,
unless there is a specific reason not to. The reason is that, we have a lot of
applications (~100), that are developed in parallel and somewhat independentlt,
but in the end, need to execute in the same execution environment. This means
we only want to deploy one version of each application. We use version-ranges
for most of our dependencies (so we do get automatic upgrades to some extent),
but we want some kind of notification, when newer versions (outside the
version-range) are available for all (including transitive) dependencies, to
help us deploy a consistent set of applications in the end.
> Add parameter to report on transitive dependencies, to
> display-dependency-updates goal
> --------------------------------------------------------------------------------------
>
> Key: MVERSIONS-102
> URL: http://jira.codehaus.org/browse/MVERSIONS-102
> Project: Maven 2.x Versions Plugin
> Issue Type: New Feature
> Affects Versions: 1.1
> Reporter: Erik Schepers
> Priority: Minor
> Attachments: MVERSIONS-102.patch
>
>
> To get a complete view of used dependency versions, it would be nice to have
> an optional {{versions.transitive}} parameter, which enables processing of
> transitive dependencies.
> I've attached a patch, including 2 integration tests, that implement and test
> this feature.
> Note that due to this patch, the {{display-dependency-updates}} now performs
> dependency-resolution up-until the test-scope.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
