[ 
http://jira.codehaus.org/browse/MVERSIONS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthew Beermann updated MVERSIONS-18:
--------------------------------------

    Attachment: MVERSIONS-18-versions-maven-plugin.patch

> Expose updated versions as a report
> -----------------------------------
>
>                 Key: MVERSIONS-18
>                 URL: http://jira.codehaus.org/browse/MVERSIONS-18
>             Project: Maven 2.x Versions Plugin
>          Issue Type: New Feature
>    Affects Versions: 1.0-alpha-2
>            Reporter: Matthew Beermann
>         Attachments: MVERSIONS-18-versions-maven-plugin.patch
>
>
> My company tasked me with creating a report that summarizes the available 
> updates to a given project's dependencies. As I was doing my research, I 
> realized that it might be a good addition to the versions-maven-plugin.
> One of the main use cases we envision is an assembler assessing the state of 
> his dependency tree just before a release, looking for updated versions to 
> pull in. Having this information available in a report makes it easily 
> available to others, even those who might not have Maven installed. As a side 
> benefit, it would also allow them to prove due diligence after the fact, i.e. 
> that they took all updates available at the time (or consciously chose to 
> ignore them).
> I've already got all the code written, and will upload it momentarily.

-- 
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


Reply via email to