[jira] Updated: (MCHANGES-192) Add an urlDownload attribute in changes.xml, similar to what can be configured for the announcement goal

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

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

Dennis Lundberg updated MCHANGES-192:
-------------------------------------

    Component/s:     (was: announcement)
                 modello
        Summary: Add an urlDownload attribute in changes.xml, similar to what can be configured for the announcement goal  (was: Allow releases to provide links to download/artifacts)

> Add an urlDownload attribute in changes.xml, similar to what can be configured for the announcement goal
> --------------------------------------------------------------------------------------------------------
>
>                 Key: MCHANGES-192
>                 URL: http://jira.codehaus.org/browse/MCHANGES-192
>             Project: Maven 2.x Changes Plugin
>          Issue Type: New Feature
>          Components: changes.xml, modello
>    Affects Versions: 2.2, 2.3
>            Reporter: Karl Palsson
>         Attachments: mchanges-192__artifacts-download-link-schema.diff
>
>
> Currently, the announcement generator has a pom level config property urlDownload which can only be specified once for the project, and the changes report built during site generation has no links for url download whatsoever.
> I propose an attribute on each release, like so...
> {code:xml}
> <release version="2.4" description="something" artifacts="http://example.org/releases/2.4">
>     <action dev="me" type="add">blah blah adding artifact links.</action>
> </release>
> {code}
> This would then generate a link in each release section.
> For the announcement mail, I'm unsure of the best way of relating these, but as a default, I propose that if urlDownload is _not_ specified, then the most recent release's artifact url is used as the urlDownload, if specified at all.
> Patch is attached, notes about the patch:
> * New schema version!  
>   --> Both 1.0.0 and 1.0.1 are generated and packaged now.
>   --> changes.mdo had to be overhauled a bit to allow generating both versions at once. Mostly 1.0.0 -> 1.0.0+
> * to take advantage of new schema, you must actually specify it in the config (see MCHANGES-191)
> * No translations for the new text: "report.changes.text.artifacts=Artifact download link:"
>  (Sorry, I don't speak french, german or swedish :)

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