You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ivan Khalopik (JIRA)" <ji...@codehaus.org> on 2011/04/21 17:46:29 UTC
[jira] Updated: (MCHANGES-76) Add an option to hava an aggregated
Changes Report
[ http://jira.codehaus.org/browse/MCHANGES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Khalopik updated MCHANGES-76:
----------------------------------
Attachment: 0001-MCHANGES-76-added-aggregated-option-to-ChangesMojo-t.patch
Solution that uses the same plugin configuration for all child modules while creating aggregated report.
Also available via GitHub pull request:
https://github.com/apache/maven-plugins/pull/3
> Add an option to hava an aggregated Changes Report
> --------------------------------------------------
>
> Key: MCHANGES-76
> URL: http://jira.codehaus.org/browse/MCHANGES-76
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: changes.xml
> Reporter: geoff simpson
> Attachments: 0001-MCHANGES-76-added-aggregated-option-to-ChangesMojo-t.patch
>
>
> Would be good to be able to scan child projects of the master pom and generated a summary based on the changes.xml files from all the children.
--
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