Hi,
We solved some issues:
** Bug
* [MCHANGES-276] - TracDownloader does not set issue key to ticket id
* [MCHANGES-293] - XML Parser error backtraces from, presumably,
malformed JIRA responses
* [MCHANGES-299] - ClassNotFoundException when running jira-report
using Maven 2.2.1
* [MCHANGES-301] - Impossible to use ParameterBasedQuery in
combination with JIRA authentication
* [MCHANGES-302] - The REST API is always used when JIRA
authentication is configured
** Improvement
* [MCHANGES-46] - There is no link to the RSS feed of changes in
the changes report
* [MCHANGES-278] - Improved logging and exception messages to aid
troubleshooting
* [MCHANGES-289] - Please add support for HTTP digest
authentication to the 'trac-report' plugin.
* [MCHANGES-290] - Provide GitHub support for generate announcement report
* [MCHANGES-295] - Remove need for numeric component ID's etc when
using REST with JIRA
** New Feature
* [MCHANGES-300] - Make it possible to run the changes-check and
changes-validate goals only once for a multi-module project
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MCHANGES%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-321/
https://repository.apache.org/content/repositories/maven-321/org/apache/maven/plugins/maven-changes-plugin/2.9/maven-changes-plugin-2.9-source-release.zip
Staging site:
http://maven.apache.org/plugins-archives/maven-changes-plugin-2.9/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
