Tomasz Pik wrote:
On 5/30/05, Vincent Massol <[EMAIL PROTECTED]> wrote:
[...]
I think we need to have the JIRA plugin working to use this approach as end
users will want to see the changes when looking at a plugin's web site.
Also, before we can move to this approach we would also need to modify the
announcement plugin to support the JIRA plugin. ATM it's using the
changes.xml file only.
Please, note that JIRA is not used in all projects.
So, using JIRA plugin to generate 'changelogs' in annocemenets results in
empty changelogs for projects not using JIRA.
We're only talking about Maven's own projects presently. No intention to
remove the changes plugin or announcement support.
Actually, I think it might be good for the JIRA plugin to create a
changes.xml file, then run it through the existing reports.
In long term I think it might be a good idea to provide some kind of abstraction
layer for issue trackers (like maven-scm for cvs/scm/other things) to cover
JIRA, mantis and other tools like this.
Good idea, volunteering? :)
We actually had that in mind - you'll see the Maven2 POM has an
"issueManagement" section with a URL and system key.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
