|
||||||||
|
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 |
||||||||
- [mojo-dev] [jira] (MVERSIONS-172) Make the versions:di... Ryan Gardner (JIRA)
- [mojo-dev] [jira] (MVERSIONS-172) Make the versio... Marc Pasteur (JIRA)

I know this is a low priority - but having forgotten that I already patched this I ran into another situation where I need this functionality and I almost patched it again (I guess I'm forgetful)
Is there any reason why display-dependency-updates should NOT allow you to filter things using the -Dincludes="" in the same way you can run the update dependency scripts with the -Dincludes=""?
The reason for this is to display what will be updated in an easy-to-understand way to a user prior to them running the update command to have it actually do it. YES it is possible to do a diff against a vcs system to see what the update command changed, but this approach seems simpler.