[ 
http://jira.codehaus.org/browse/MCHANGES-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=270738#comment-270738
 ] 

Dennis Lundberg commented on MCHANGES-58:
-----------------------------------------

I have already started to look at the patches that we have for "other 
issuetrackers". Some of the patches are old and might not apply cleanly. The 
code has undergone some major refactoring in recent time, so getting the 
patches incorporated into the current source will be challenging.

Currently my open source time is limited, but this is something that I've 
wanted to do for a long time. My plan is to create some kind of high level API 
for interacting with issue management systems (IMS). That API will be on a much 
higher abstraction level than Mylyn. But there might be a place for Mylyn 
somewhere under the hood of that API.

Another thing we need to solve is configuration of the different Mojos. For 
every new IMS we duplicate a lot of Mojo code. We need to figure out a better 
and more general way to configure an IMS. In an ideal world we would have only 
one IssueReportMojo that works for all supported IMSes. Currently that means 
JIRA and Trac, but going forward it would also need to work for Bugzilla and 
Google Code, which also has some possible code (MCHANGES-142).



> Add ability to manage Bugzilla instead of JIRA
> ----------------------------------------------
>
>                 Key: MCHANGES-58
>                 URL: http://jira.codehaus.org/browse/MCHANGES-58
>             Project: Maven 2.x Changes Plugin
>          Issue Type: New Feature
>          Components: other issue-trackers
>            Reporter: Damien Lecan
>         Attachments: MCHANGES-58-maven-changes-plugin.patch
>
>
> It would be very nice if this plugin can manage Bugzilla as it does for JIRA

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to