You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joseph Walton (JIRA)" <ji...@codehaus.org> on 2012/07/26 05:25:21 UTC
[jira] (MDEP-361) dependency:tree's use of "version selected from
constraint" is too verbose
Joseph Walton created MDEP-361:
----------------------------------
Summary: dependency:tree's use of "version selected from constraint" is too verbose
Key: MDEP-361
URL: https://jira.codehaus.org/browse/MDEP-361
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Affects Versions: 2.5
Reporter: Joseph Walton
MDEP-339's fix increases the level of verbosity in the dependency tree to include the specified constraint as well as the actual version. In many builds, these will be identical.
{noformat}
[INFO] | +- commons-lang:commons-lang:jar:2.4:compile (scope managed from 2.4; version selected from constraint 2.4)
{noformat}
The format change makes diffing the old and new versions difficult to see what behaviour has changed. In the case where the constraint is the same as the version it doesn't seem to add much information.
I'd suggest omitting it when the version exactly matches the constraint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-361) dependency:tree's use of "version selected from
constraint" is too verbose
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed MDEP-361.
------------------------------
Resolution: Cannot Reproduce
Assignee: Herve Boutemy
AFAIK, this is fixed since [r1365268|http://svn.apache.org/viewvc?rev=1365268&view=rev], and checked by tree it
> dependency:tree's use of "version selected from constraint" is too verbose
> --------------------------------------------------------------------------
>
> Key: MDEP-361
> URL: https://jira.codehaus.org/browse/MDEP-361
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Affects Versions: 2.5
> Reporter: Joseph Walton
> Assignee: Herve Boutemy
> Attachments: 0001-MDEP-361-Only-print-versions-that-differ-from-their-.patch
>
>
> MDEP-339's fix increases the level of verbosity in the dependency tree to include the specified constraint as well as the actual version. In many builds, these will be identical.
> {noformat}
> [INFO] | +- commons-lang:commons-lang:jar:2.4:compile (scope managed from 2.4; version selected from constraint 2.4)
> {noformat}
> The format change makes diffing the old and new versions difficult to see what behaviour has changed. In the case where the constraint is the same as the version it doesn't seem to add much information.
> I'd suggest omitting it when the version exactly matches the constraint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-361) dependency:tree's use of "version selected from
constraint" is too verbose
Posted by "Joseph Walton (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=305113#comment-305113 ]
Joseph Walton commented on MDEP-361:
------------------------------------
Yes, confirming that the change fixes this issue for me, and also shows the constraint when it's a range. Thanks.
> dependency:tree's use of "version selected from constraint" is too verbose
> --------------------------------------------------------------------------
>
> Key: MDEP-361
> URL: https://jira.codehaus.org/browse/MDEP-361
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Affects Versions: 2.5
> Reporter: Joseph Walton
> Assignee: Herve Boutemy
> Attachments: 0001-MDEP-361-Only-print-versions-that-differ-from-their-.patch
>
>
> MDEP-339's fix increases the level of verbosity in the dependency tree to include the specified constraint as well as the actual version. In many builds, these will be identical.
> {noformat}
> [INFO] | +- commons-lang:commons-lang:jar:2.4:compile (scope managed from 2.4; version selected from constraint 2.4)
> {noformat}
> The format change makes diffing the old and new versions difficult to see what behaviour has changed. In the case where the constraint is the same as the version it doesn't seem to add much information.
> I'd suggest omitting it when the version exactly matches the constraint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-361) dependency:tree's use of "version selected from
constraint" is too verbose
Posted by "Joseph Walton (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Walton updated MDEP-361:
-------------------------------
Attachment: 0001-MDEP-361-Only-print-versions-that-differ-from-their-.patch
This patch omits the constraint when identical to the resolved version. In testing with Maven 3, they were identical even when the POM specified a range.
> dependency:tree's use of "version selected from constraint" is too verbose
> --------------------------------------------------------------------------
>
> Key: MDEP-361
> URL: https://jira.codehaus.org/browse/MDEP-361
> Project: Maven 2.x Dependency Plugin
> Issue Type: Improvement
> Affects Versions: 2.5
> Reporter: Joseph Walton
> Attachments: 0001-MDEP-361-Only-print-versions-that-differ-from-their-.patch
>
>
> MDEP-339's fix increases the level of verbosity in the dependency tree to include the specified constraint as well as the actual version. In many builds, these will be identical.
> {noformat}
> [INFO] | +- commons-lang:commons-lang:jar:2.4:compile (scope managed from 2.4; version selected from constraint 2.4)
> {noformat}
> The format change makes diffing the old and new versions difficult to see what behaviour has changed. In the case where the constraint is the same as the version it doesn't seem to add much information.
> I'd suggest omitting it when the version exactly matches the constraint.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira