Maven 2.x Changes Plugin

Add ability to manage Bugzilla instead of JIRA

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: other issue-trackers
  • Labels:
    None
  • Number of attachments :
    1

Description

It would be very nice if this plugin can manage Bugzilla as it does for JIRA

Issue Links

depends upon

New Feature - A new feature of the product, which has yet to be developed. MCHANGES-85 Create an abstraction layer for issue tracking systems

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.
is related to

New Feature - A new feature of the product, which has yet to be developed. MCHANGES-59 Add ability to manage Trac instead of JIRA

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Francois Le Fevre added a comment -

I totally agree, JIRA is a commercial bugzilla!!

Show
Francois Le Fevre added a comment - I totally agree, JIRA is a commercial bugzilla!!
Hide
Permalink
Dennis Lundberg added a comment -

Since the Maven project uses JIRA for its own issue management, it is unlikely that anyone on the team has a strong need for this functionality. The best way of getting this issue resolved is by providing a patch. I can help out by answering any questions that might arise.

Show
Dennis Lundberg added a comment - Since the Maven project uses JIRA for its own issue management, it is unlikely that anyone on the team has a strong need for this functionality. The best way of getting this issue resolved is by providing a patch. I can help out by answering any questions that might arise.
Hide
Permalink
Damien Lecan added a comment -

?
As I see that Maven SCM project manages a lot of SCM's, may I conclude that Maven project uses CVS, Subversion, Perforce, Clearcase and VSS all together ?

I understand your point of view, but I am a disappointed by a such answer.

Building a patch for this feature is a huge work, especilly because many business rules could be shared between Jira and BZ implementations (many of AbstractJiraDownloader methods could be used for BZ too).

It is not possible to do refactoring with patch, they are too hard to maintain.

Show
Damien Lecan added a comment - ? As I see that Maven SCM project manages a lot of SCM's, may I conclude that Maven project uses CVS, Subversion, Perforce, Clearcase and VSS all together ? I understand your point of view, but I am a disappointed by a such answer. Building a patch for this feature is a huge work, especilly because many business rules could be shared between Jira and BZ implementations (many of AbstractJiraDownloader methods could be used for BZ too). It is not possible to do refactoring with patch, they are too hard to maintain.
Hide
Permalink
Mark Hobson added a comment -

There was a thread a while ago on maven-dev regarding sharing Bugzilla communication code with the Eclipse Mylar project, which would make this a lot easier.

Show
Mark Hobson added a comment - There was a thread a while ago on maven-dev regarding sharing Bugzilla communication code with the Eclipse Mylar project, which would make this a lot easier.
Hide
Permalink
Damien Lecan added a comment -

Very interesting !
Starting point : http://mail-archives.apache.org/mod_mbox//maven-dev/200607.mbox/%3cc184d750607030907k59f7c8c0vcdaa64f0d9036e42@mail.gmail.com%3e

What is the status of this new API ? Is it available somewhere ?

If yes, does this plugin plans to migrate ? I have seen that another request was done for Trac instead of JIRA too (MCHANGES-59).

Show
Damien Lecan added a comment - Very interesting ! Starting point : http://mail-archives.apache.org/mod_mbox//maven-dev/200607.mbox/%3cc184d750607030907k59f7c8c0vcdaa64f0d9036e42@mail.gmail.com%3e What is the status of this new API ? Is it available somewhere ? If yes, does this plugin plans to migrate ? I have seen that another request was done for Trac instead of JIRA too ( MCHANGES-59 ).
Hide
Permalink
Mark Hobson added a comment -

The abstract issue API to use would be Mylar's, since a lot of work has been put into that and it's various implementations - check the Mylar CVS. I seem to remember the above thread ending with requirement to build Mylar with Maven, so it's artifacts can be used by Maven components. I meant to raise an issue with Mylar as Mik suggested..

Show
Mark Hobson added a comment - The abstract issue API to use would be Mylar's, since a lot of work has been put into that and it's various implementations - check the Mylar CVS. I seem to remember the above thread ending with requirement to build Mylar with Maven, so it's artifacts can be used by Maven components. I meant to raise an issue with Mylar as Mik suggested..
Hide
Permalink
Mark Hobson added a comment -

Finally got around to it

https://bugs.eclipse.org/bugs/show_bug.cgi?id=166203

Show
Mark Hobson added a comment - Finally got around to it https://bugs.eclipse.org/bugs/show_bug.cgi?id=166203
Hide
Permalink
Dennis Lundberg added a comment -

Damien,

The purpose of my comment was to set your expectations at a reasonable level. If it came across in any other way I apologize. The knowledge of Bugzilla among the Maven devs is probably lower than it is for JIRA, so we would probably need help from the some Bugilla power-users in the community to pull this off.

The comparison to Maven SCM is both a good and a bad one. Maven SCM does have the abstraction layer that is need for this to work in a smooth way, and that Mark talks about. The discussions about this on the dev-list sort of ended in, well not much. If the effort to create such an interface is pushed through I would certainly be interested in using it in this plugin.

However the issue tracking system is used for reporting only in Maven, while SCM is used for releasing stuff. So it has, and should have, a higher priority. Reporting won't do you much good if you can't build or release your project.

Show
Dennis Lundberg added a comment - Damien, The purpose of my comment was to set your expectations at a reasonable level. If it came across in any other way I apologize. The knowledge of Bugzilla among the Maven devs is probably lower than it is for JIRA, so we would probably need help from the some Bugilla power-users in the community to pull this off. The comparison to Maven SCM is both a good and a bad one. Maven SCM does have the abstraction layer that is need for this to work in a smooth way, and that Mark talks about. The discussions about this on the dev-list sort of ended in, well not much. If the effort to create such an interface is pushed through I would certainly be interested in using it in this plugin. However the issue tracking system is used for reporting only in Maven, while SCM is used for releasing stuff. So it has, and should have, a higher priority. Reporting won't do you much good if you can't build or release your project.
Hide
Permalink
Matthew Beermann added a comment -

Now that Mylyn is available in the central repository [1], I started working on this bug. In fact, I finished it, but then ran into a major snag: the Mylyn libraries were compiled against and require Java 5. As far as I know, Maven still enforces Java 1.4 compatibility on all plugins (but feel free to correct me). Any ideas how to work around this?

[1] http://repo1.maven.org/eclipse/org/eclipse/mylyn/

Show
Matthew Beermann added a comment - Now that Mylyn is available in the central repository [1] , I started working on this bug. In fact, I finished it, but then ran into a major snag: the Mylyn libraries were compiled against and require Java 5. As far as I know, Maven still enforces Java 1.4 compatibility on all plugins (but feel free to correct me). Any ideas how to work around this? [1] http://repo1.maven.org/eclipse/org/eclipse/mylyn/
Hide
Permalink
Matthew Beermann added a comment -

Here's my patch, for posterity's (and backup's) sake. Note that it requires -Dmaven.compiler.source=1.5

Show
Matthew Beermann added a comment - Here's my patch, for posterity's (and backup's) sake. Note that it requires -Dmaven.compiler.source=1.5
Hide
Permalink
Mark Hobson added a comment -

I'd be happy with having Java5 as a prerequisite for users requiring the Bugzilla side of maven-changes-plugin - maybe worth taking to the dev list for discussion?

Show
Mark Hobson added a comment - I'd be happy with having Java5 as a prerequisite for users requiring the Bugzilla side of maven-changes-plugin - maybe worth taking to the dev list for discussion?
Hide
Permalink
Philip Maher added a comment - - edited

Now that the changes plugin requires Java 5 can the patch for Bugzilla be applied?

Show
Philip Maher added a comment - - edited Now that the changes plugin requires Java 5 can the patch for Bugzilla be applied?
Hide
Permalink
Benson Margulies added a comment -

I just added some modularity for multiple systems. Could you please revise to work with it?

Show
Benson Margulies added a comment - I just added some modularity for multiple systems. Could you please revise to work with it?
Hide
Permalink
Dennis Lundberg added a comment -

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).

Show
Dennis Lundberg added a comment - 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 ).

People

  • Assignee:
    Unassigned
    Reporter:
    Damien Lecan
Vote (15)
Watch (15)

Dates

  • Created:
    Updated: