michael-o commented on PR #23: URL: https://github.com/apache/maven-changes-plugin/pull/23#issuecomment-1246381242
> > consider remove everything which needs online access > > Although I understand the point, there is currently neither an alternative for generating reports from JIRA nor from Trac. WDYT about splitting it up, i.e. add a `maven-jira-changes-plugin` which generates the `changes.xml` which is subsequently picked up by `maven-changes-plugin` to generate the according pages? Similarly other issue tracker systems could be supported by dedicated plugins. I understand that, but testing here is really hard, mostly impossible, at least for me. I pretty much like the idea. As a build plugin, this would work, but how to do this with a reporting plugin? Because MSITE will execute both... Maybe rather the code on MCHANGES should be retrofitted to be used as a plugin and as a plugin. The specific issue tracker plugin would use MCHANGES as a dependency to generate the report. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
