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

Michael Osipov closed MCHANGES-192.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period 
of time. If you think this issue still applies, retest your problem with the 
most recent version of Maven and the affected component, reopen and post your 
results.

> Add an urlDownload attribute in changes.xml, similar to what can be 
> configured for the announcement goal
> --------------------------------------------------------------------------------------------------------
>
>                 Key: MCHANGES-192
>                 URL: https://issues.apache.org/jira/browse/MCHANGES-192
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to