Well, the JIRA report code is old and does not support JIRA 3.x. It would need a little work to get working with 3.x and given that there is a new issue tracking reporting subsystem being worked on, I figured it was simpler to just kill the code rather than maintain it. I wouldn't have a problem leaving the code where it is if you could disable it except that with the site plugin, every report in a report plugin always generates AFAIK so there is no way to generate the changes report without running the JIRA report, save resorting to a "disableJiraReport" config parameter hack.
mike -----Original Message----- From: Kris Bravo [mailto:[EMAIL PROTECTED] Sent: Monday, January 23, 2006 10:02 PM To: dev@mojo.codehaus.org Subject: Re: [mojo-dev] Remove JIRA report from changes-maven-plugin Without having looked at the code for obvious issues, could you educate me on the motivaction for the split? On Mon, 2006-01-23 at 20:56 -0600, Mike Perham wrote: > I'd like to propose removing the JIRA report from the > changes-maven-plugin. I think this report would be much better suited > packaged into another issue management reporting plugin whereas the > changes plugin is devoted to reporting on a simple developer-authored > changelog. > > I'll take 48 hrs of silence as consent. If you are using this > functionality or have a problem with this move for other reasons, > please speak up. > > mike
