You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Mark Hobson <ma...@gmail.com> on 2006/07/03 18:07:47 UTC
Common API for issue tracking systems
Hi there,
I was wondering whether any thought had been given to an abstract
issue tracking API with implementations for Bugzilla, JIRA, etc.? I
can see a couple of uses within maven:
* Querying the issues fixed when releasing a new version of a project,
to be used within the maven-changes-plugin
* Creating a new version of a product in the underlying issue tracking
system when releasing a new version of a project
I couldn't see this abstraction in the maven-changes-plugin, but
correct me if I'm wrong.
I've recently written some code to programmatically manipulate
Bugzilla, and thought this could be expanded into a general-purpose
abstract API for manipulating issue tracking systems. Rather like
Wagon is to transports and SCM is to SCMs.
It'd be good to see Bugzilla support within maven and I'd be
interested in people's thoughts.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Jeff Turner <je...@apache.org>.
On Mon, Jul 03, 2006 at 05:07:47PM +0100, Mark Hobson wrote:
> Hi there,
>
> I was wondering whether any thought had been given to an abstract
> issue tracking API with implementations for Bugzilla, JIRA, etc.?
>
> I can see a couple of uses within maven:
>
> * Querying the issues fixed when releasing a new version of a project,
> to be used within the maven-changes-plugin
>
> * Creating a new version of a product in the underlying issue tracking
> system when releasing a new version of a project
>
> I couldn't see this abstraction in the maven-changes-plugin, but
> correct me if I'm wrong.
>
> I've recently written some code to programmatically manipulate
> Bugzilla, and thought this could be expanded into a general-purpose
> abstract API for manipulating issue tracking systems. Rather like
> Wagon is to transports and SCM is to SCMs.
As a maintainer of JIRA's Mantis and Bugzilla importers, I've frequently
wished for a common data model or API. It's crazy that there is no
way to migrate data from tracker X to tracker Y, unless Y has a custom
importer, or both support CSV (and you're happy to lose half the info).
Migrating data between systems is a very different use-case to yours
though. Both would benefit from a common API or data model, but importers
would focus on the nouns, while a Maven plugin would focus on the verbs.
--Jeff
> It'd be good to see Bugzilla support within maven and I'd be
> interested in people's thoughts.
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Mark Hobson <ma...@gmail.com>.
On 04/07/06, Jochen Wiedmann <jo...@gmail.com> wrote:
> An XML-RPC API is in the works. AFAIK, it's on the roadmap for Bugzilla 2.24.
You're right, I wasn't aware of this thanks:
https://bugzilla.mozilla.org/show_bug.cgi?id=224577
Should make the bugzilla implementation *alot* easier.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Jochen Wiedmann <jo...@gmail.com>.
On 7/4/06, Mark Hobson <ma...@gmail.com> wrote:
> both projects could share the same abstraction. Communication with
> Bugzilla is rather tedious and Mylar's implementation seems quite
> comprehensive.
An XML-RPC API is in the works. AFAIK, it's on the roadmap for Bugzilla 2.24.
Jochen
--
Whenever you find yourself on the side of the
majority, it is time to pause and reflect.
(Mark Twain)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Mark Hobson <ma...@gmail.com>.
Cool, good to see things are moving in that direction. I did think
Mylar was the closest out there to what was needed - it'd be good if
both projects could share the same abstraction. Communication with
Bugzilla is rather tedious and Mylar's implementation seems quite
comprehensive.
Mark
On 04/07/06, Brett Porter <br...@apache.org> wrote:
> We should also mention that it has already been started in the Maven
> sandbox.
>
> - Brett
>
> On 4/07/2006 4:04 AM, Jason van Zyl wrote:
> > Hi,
> >
> > One person who should definitely be pulled into the discussion is Mik
> > Kersten. He's the fellow who works on Mylar and has integration for
> > Bugzilla and JIRA and I think Mantis. He's got some code that would
> > definitely be of use.
> >
> > Mik, are you interested creating a general library for issue management
> > here?
> >
> > Sorry for just pulling you in here but I figure it's just easier to get
> > you involved as the topic has come up :-)
> >
> > Jason.
> >
> >
> > On 3 Jul 06, at 5:07 PM 3 Jul 06, Mark Hobson wrote:
> >
> >> Hi there,
> >>
> >> I was wondering whether any thought had been given to an abstract
> >> issue tracking API with implementations for Bugzilla, JIRA, etc.? I
> >> can see a couple of uses within maven:
> >>
> >> * Querying the issues fixed when releasing a new version of a project,
> >> to be used within the maven-changes-plugin
> >>
> >> * Creating a new version of a product in the underlying issue tracking
> >> system when releasing a new version of a project
> >>
> >> I couldn't see this abstraction in the maven-changes-plugin, but
> >> correct me if I'm wrong.
> >>
> >> I've recently written some code to programmatically manipulate
> >> Bugzilla, and thought this could be expanded into a general-purpose
> >> abstract API for manipulating issue tracking systems. Rather like
> >> Wagon is to transports and SCM is to SCMs.
> >>
> >> It'd be good to see Bugzilla support within maven and I'd be
> >> interested in people's thoughts.
> >>
> >> Cheers,
> >>
> >> Mark
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> > Jason van Zyl
> > jason@maven.org
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
>
> --
> Brett Porter <br...@apache.org>
> Apache Maven - http://maven.apache.org/
> Better Builds with Maven - http://library.mergere.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Brett Porter <br...@apache.org>.
We should also mention that it has already been started in the Maven
sandbox.
- Brett
On 4/07/2006 4:04 AM, Jason van Zyl wrote:
> Hi,
>
> One person who should definitely be pulled into the discussion is Mik
> Kersten. He's the fellow who works on Mylar and has integration for
> Bugzilla and JIRA and I think Mantis. He's got some code that would
> definitely be of use.
>
> Mik, are you interested creating a general library for issue management
> here?
>
> Sorry for just pulling you in here but I figure it's just easier to get
> you involved as the topic has come up :-)
>
> Jason.
>
>
> On 3 Jul 06, at 5:07 PM 3 Jul 06, Mark Hobson wrote:
>
>> Hi there,
>>
>> I was wondering whether any thought had been given to an abstract
>> issue tracking API with implementations for Bugzilla, JIRA, etc.? I
>> can see a couple of uses within maven:
>>
>> * Querying the issues fixed when releasing a new version of a project,
>> to be used within the maven-changes-plugin
>>
>> * Creating a new version of a product in the underlying issue tracking
>> system when releasing a new version of a project
>>
>> I couldn't see this abstraction in the maven-changes-plugin, but
>> correct me if I'm wrong.
>>
>> I've recently written some code to programmatically manipulate
>> Bugzilla, and thought this could be expanded into a general-purpose
>> abstract API for manipulating issue tracking systems. Rather like
>> Wagon is to transports and SCM is to SCMs.
>>
>> It'd be good to see Bugzilla support within maven and I'd be
>> interested in people's thoughts.
>>
>> Cheers,
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> Jason van Zyl
> jason@maven.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Jason van Zyl <ja...@maven.org>.
Nice!
On 29 Nov 06, at 9:16 AM 29 Nov 06, Mark Hobson wrote:
> On 07/07/06, Mik Kersten <be...@acm.org> wrote:
>> There should be no problem. Just file a Mylar bug report with the
>> structure
>> you want and we can iterate from there. If the easiest way to do
>> that is
>> for us to build those JARs via Maven instead of plain Ant I'm
>> happy to do
>> that too.
>
> Finally got around to raising a bug against Mylar for a Maven build:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=166203
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Mark Hobson <ma...@gmail.com>.
On 07/07/06, Mik Kersten <be...@acm.org> wrote:
> There should be no problem. Just file a Mylar bug report with the structure
> you want and we can iterate from there. If the easiest way to do that is
> for us to build those JARs via Maven instead of plain Ant I'm happy to do
> that too.
Finally got around to raising a bug against Mylar for a Maven build:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=166203
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Common API for issue tracking systems
Posted by Mik Kersten <be...@acm.org>.
-----Original Message-----
> From: Tomasz Pik [mailto:tompik@gmail.com]
...
> Yes. But this brings up a bigger question about providing jars
> in a way that Maven will be able to use (which means a repository
> with given layout of directories/fiels) - is there a way to setup such
> a thing on eclipse.org infrastructure?
> I don't know if this thread is a good place to start such a discussion.
There should be no problem. Just file a Mylar bug report with the structure
you want and we can iterate from there. If the easiest way to do that is
for us to build those JARs via Maven instead of plain Ant I'm happy to do
that too.
> I remember that somebody (Brett?) was talking with one of eclipse
> projects (PDE?) about switching their builds to maven so maybe
> in future this project will provide it's jars in maven way 'out of the
> box'.
That could be interesting, and the right place to prototype it seems like
the Eclipse Maven Plug-in and then try to get it pulled up to PDE. But note
that the PDE's build is tightly coupled to the plugin.xml/OSGi model that
Eclipse uses, so that might need to be made reusable or re-implemented in
Maven. Either way it's orthogonal to this effort, but it would be great to
see more cooperation between Maven and Eclipse projects.
> Pehaps we should move disussion about this to more appopriate place,
> mylar newsgroup or 'dev' list?
Yes, we have most of our interaction on bug reports so please file one,
anyone interested can add themselves as a CC. Once you do that I'll ping
mylar-dev in case others are interested in the discussion.
Mik
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Tomasz Pik <to...@gmail.com>.
On 7/7/06, Mik Kersten <be...@acm.org> wrote:
> Eclipse.org provides us with an excellent download infrastructure and
> mirroring system, so it's probably simplest to use that. It would make
> bundling the JARs and maintaining dependencies Mylar's responsibility.
> Anything extra you would need (i.e. the poms) would be best as a
> contribution you make to the Ant build script. Would that work?
Yes. But this brings up a bigger question about providing jars
in a way that Maven will be able to use (which means a repository
with given layout of directories/fiels) - is there a way to setup such
a thing on eclipse.org infrastructure?
I don't know if this thread is a good place to start such a discussion.
I remember that somebody (Brett?) was talking with one of eclipse
projects (PDE?) about switching their builds to maven so maybe
in future this project will provide it's jars in maven way 'out of the
box'.
> Note that 0.6.0 is not ready for being used in this way because it has the
> Tasks API in the mylar.tasklist, which is coupled into the UI. Bug for that
> is:
>
> 149981: extract tasks framework from mylar.tasklist
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=149981
Pehaps we should move disussion about this to more appopriate place,
mylar newsgroup or 'dev' list?
Regards,
Tomek
> Mik
>
> > -----Original Message-----
> > From: Tomasz Pik [mailto:tompik@gmail.com]
> > Sent: Friday, July 07, 2006 1:45 AM
> > To: Mik Kersten
> > Cc: brett@maven.org; Maven Developers List
> > Subject: Re: Common API for issue tracking systems
> >
> > On 7/7/06, Mik Kersten <be...@acm.org> wrote:
> >
> > > Could you please create a bug report for us to indicate how you want to
> > get
> > > this API, e.g. have a downloadable bin+src JAR, separate JARs, build
> > from
> > > source? http://www.eclipse.org/mylar/bugs.php
> >
> > Ideally I'd like just to define, that my code depends on mylar libraries
> > and maven will download them from ibblio mirrors.
> > But this comes down to disussion about maintaining libraries on
> > ibiblio, I don't know if mylar team is interested in providing jars
> > and poms in a needed form.
> > Please, let me know this, otherwise I'll try to prepare such set
> > based on mylar 0.6.0 distribution and open an issue for adding them
> > to ibiblio (perhaps asking Mylar team to review dependencies and other
> > things first).
> >
> > Regards,
> > Tomek
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Common API for issue tracking systems
Posted by Jeff Jensen <je...@upstairstechnology.com>.
An issue hosting artifacts not on ibiblio is the Maven group has tried to
centralize on ibiblio so we all don't have to have dozens of different repos
in our config.
-----Original Message-----
From: Mik Kersten [mailto:beatmik@acm.org]
Sent: Friday, July 07, 2006 9:38 AM
To: 'Tomasz Pik'
Cc: brett@maven.org; 'Maven Developers List'
Subject: RE: Common API for issue tracking systems
Eclipse.org provides us with an excellent download infrastructure and
mirroring system, so it's probably simplest to use that. It would make
bundling the JARs and maintaining dependencies Mylar's responsibility.
Anything extra you would need (i.e. the poms) would be best as a
contribution you make to the Ant build script. Would that work?
Note that 0.6.0 is not ready for being used in this way because it has the
Tasks API in the mylar.tasklist, which is coupled into the UI. Bug for that
is:
149981: extract tasks framework from mylar.tasklist
https://bugs.eclipse.org/bugs/show_bug.cgi?id=149981
Mik
> -----Original Message-----
> From: Tomasz Pik [mailto:tompik@gmail.com]
> Sent: Friday, July 07, 2006 1:45 AM
> To: Mik Kersten
> Cc: brett@maven.org; Maven Developers List
> Subject: Re: Common API for issue tracking systems
>
> On 7/7/06, Mik Kersten <be...@acm.org> wrote:
>
> > Could you please create a bug report for us to indicate how you want
> > to
> get
> > this API, e.g. have a downloadable bin+src JAR, separate JARs, build
> from
> > source? http://www.eclipse.org/mylar/bugs.php
>
> Ideally I'd like just to define, that my code depends on mylar
> libraries and maven will download them from ibblio mirrors.
> But this comes down to disussion about maintaining libraries on
> ibiblio, I don't know if mylar team is interested in providing jars
> and poms in a needed form.
> Please, let me know this, otherwise I'll try to prepare such set based
> on mylar 0.6.0 distribution and open an issue for adding them to
> ibiblio (perhaps asking Mylar team to review dependencies and other
> things first).
>
> Regards,
> Tomek
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Common API for issue tracking systems
Posted by Mik Kersten <be...@acm.org>.
Eclipse.org provides us with an excellent download infrastructure and
mirroring system, so it's probably simplest to use that. It would make
bundling the JARs and maintaining dependencies Mylar's responsibility.
Anything extra you would need (i.e. the poms) would be best as a
contribution you make to the Ant build script. Would that work?
Note that 0.6.0 is not ready for being used in this way because it has the
Tasks API in the mylar.tasklist, which is coupled into the UI. Bug for that
is:
149981: extract tasks framework from mylar.tasklist
https://bugs.eclipse.org/bugs/show_bug.cgi?id=149981
Mik
> -----Original Message-----
> From: Tomasz Pik [mailto:tompik@gmail.com]
> Sent: Friday, July 07, 2006 1:45 AM
> To: Mik Kersten
> Cc: brett@maven.org; Maven Developers List
> Subject: Re: Common API for issue tracking systems
>
> On 7/7/06, Mik Kersten <be...@acm.org> wrote:
>
> > Could you please create a bug report for us to indicate how you want to
> get
> > this API, e.g. have a downloadable bin+src JAR, separate JARs, build
> from
> > source? http://www.eclipse.org/mylar/bugs.php
>
> Ideally I'd like just to define, that my code depends on mylar libraries
> and maven will download them from ibblio mirrors.
> But this comes down to disussion about maintaining libraries on
> ibiblio, I don't know if mylar team is interested in providing jars
> and poms in a needed form.
> Please, let me know this, otherwise I'll try to prepare such set
> based on mylar 0.6.0 distribution and open an issue for adding them
> to ibiblio (perhaps asking Mylar team to review dependencies and other
> things first).
>
> Regards,
> Tomek
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Tomasz Pik <to...@gmail.com>.
On 7/7/06, Mik Kersten <be...@acm.org> wrote:
> Could you please create a bug report for us to indicate how you want to get
> this API, e.g. have a downloadable bin+src JAR, separate JARs, build from
> source? http://www.eclipse.org/mylar/bugs.php
Ideally I'd like just to define, that my code depends on mylar libraries
and maven will download them from ibblio mirrors.
But this comes down to disussion about maintaining libraries on
ibiblio, I don't know if mylar team is interested in providing jars
and poms in a needed form.
Please, let me know this, otherwise I'll try to prepare such set
based on mylar 0.6.0 distribution and open an issue for adding them
to ibiblio (perhaps asking Mylar team to review dependencies and other
things first).
Regards,
Tomek
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Milos Kleint <mk...@gmail.com>.
Just wondering, I'm not familiar with eclipse sourcebase.
If maven uses some eclipse APIs, thus using some eclipse binaries in
non-eclipse way (no osgi/plugin encapsulation) and then we use the
maven binaries in an eclipse plugin, can we get in trouble? (by having
2 versions of same binaries on classpath etc?)
Milos
On 7/7/06, Mik Kersten <be...@acm.org> wrote:
> > -----Original Message-----
> > From: Tomasz Pik [mailto:tompik@gmail.com]
> ...
> > So it seems that the roadmap will be:
> > * Mylar project will provide 'Abstraction API' for and implementations for
> > various trackers;
>
> Yes, Mylar will provide this via it's Tasks API which has abstractions for
> repositories and tasks (what we call them from the programmers' point of
> view, aka bugs/issues/tickets). Mylar provides 3 Connectors that extend
> this API to Bugzilla, JIRA, and Trac.
>
> > * Maven wil use those libraries in plugins that will deal with trackers
> > right?
> > Or you're going to move 'generic task/issue mgmt API' out of Mylar,
> > to somewhere elese (Maven Issue projects/Codehaus ? :)
>
> Maven can use the API and Connectors, as well as creating connectors of its'
> own. The API needs to stay in the Mylar project because it is one of the
> core things that the project provides and our Eclipse UI stuff is built on
> it (it is difficult for eclipse.org projects to have external dependencies).
> But the goal here is to make it easy and convenient for Maven and others to
> reuse.
>
> Could you please create a bug report for us to indicate how you want to get
> this API, e.g. have a downloadable bin+src JAR, separate JARs, build from
> source? http://www.eclipse.org/mylar/bugs.php
>
> > -----Original Message-----
> > From: Brett Porter [mailto:brett@maven.org]
> ...
> > As far as Maven consuming it, that would work. JRE 5 is a higher
> > requirement than we currently have, but we can look at that. I assume
> > the eclipse runtime is just support code that will work outside of
> > Eclipse?
>
> Yes, the Eclipse runtime stuff will be minimal, small, and work outside of
> Eclipse. We rely pretty heavily on generics, hence the JRE 5 requirement.
> If it turns out to be something your users complain about we could consider
> using retroweaver or something similar to produce binaries that run on 1.4,
> but hopefully this will be a non-issue.
>
> > The main concern in the long term would be the license. If it is at
> > Eclipse and under the EPL, then we will only be able to use it in binary
> > form - which means any modifications or adjustments for Maven will need
> > to go through Mylar.
> >
> > Of course, I'm sure you would be more than welcome to bring the API to
> > Maven to work on as well!
>
> Yes, it is all EPL based. But we are very responsive on applying patches
> (e.g. see log at http://www.eclipse.org/mylar/doc/mylar-iplog.csv) so
> getting your API and other changes in should pose no problem. And this will
> be a good time to be getting your input and contributions to help ensure the
> Tasks API works for headless apps.
>
> Let me know if you have any other concerns, otherwise I expect that we can
> get this packaging to you within a week or two.
>
> Mik
>
> --
> Mik Kersten, http://kerstens.org/mik
> Mylar Project Lead, http://eclipse.org/mylar
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Common API for issue tracking systems
Posted by Mik Kersten <be...@acm.org>.
> -----Original Message-----
> From: Tomasz Pik [mailto:tompik@gmail.com]
...
> So it seems that the roadmap will be:
> * Mylar project will provide 'Abstraction API' for and implementations for
> various trackers;
Yes, Mylar will provide this via it's Tasks API which has abstractions for
repositories and tasks (what we call them from the programmers' point of
view, aka bugs/issues/tickets). Mylar provides 3 Connectors that extend
this API to Bugzilla, JIRA, and Trac.
> * Maven wil use those libraries in plugins that will deal with trackers
> right?
> Or you're going to move 'generic task/issue mgmt API' out of Mylar,
> to somewhere elese (Maven Issue projects/Codehaus ? :)
Maven can use the API and Connectors, as well as creating connectors of its'
own. The API needs to stay in the Mylar project because it is one of the
core things that the project provides and our Eclipse UI stuff is built on
it (it is difficult for eclipse.org projects to have external dependencies).
But the goal here is to make it easy and convenient for Maven and others to
reuse.
Could you please create a bug report for us to indicate how you want to get
this API, e.g. have a downloadable bin+src JAR, separate JARs, build from
source? http://www.eclipse.org/mylar/bugs.php
> -----Original Message-----
> From: Brett Porter [mailto:brett@maven.org]
...
> As far as Maven consuming it, that would work. JRE 5 is a higher
> requirement than we currently have, but we can look at that. I assume
> the eclipse runtime is just support code that will work outside of
> Eclipse?
Yes, the Eclipse runtime stuff will be minimal, small, and work outside of
Eclipse. We rely pretty heavily on generics, hence the JRE 5 requirement.
If it turns out to be something your users complain about we could consider
using retroweaver or something similar to produce binaries that run on 1.4,
but hopefully this will be a non-issue.
> The main concern in the long term would be the license. If it is at
> Eclipse and under the EPL, then we will only be able to use it in binary
> form - which means any modifications or adjustments for Maven will need
> to go through Mylar.
>
> Of course, I'm sure you would be more than welcome to bring the API to
> Maven to work on as well!
Yes, it is all EPL based. But we are very responsive on applying patches
(e.g. see log at http://www.eclipse.org/mylar/doc/mylar-iplog.csv) so
getting your API and other changes in should pose no problem. And this will
be a good time to be getting your input and contributions to help ensure the
Tasks API works for headless apps.
Let me know if you have any other concerns, otherwise I expect that we can
get this packaging to you within a week or two.
Mik
--
Mik Kersten, http://kerstens.org/mik
Mylar Project Lead, http://eclipse.org/mylar
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Tomasz Pik <to...@gmail.com>.
On 7/4/06, Mik Kersten <be...@acm.org> wrote:
> Thanks for pulling me in Jason, this is good timing. In terms of Mylar's
> 'Connectors' we currently have a robust and well tested framework for
> querying Bugzilla and JIRA. Trac will be ready for experimentation within a
> week or so, and no, there is no Mantis connector yet. The Bugzilla
> connector is already being used headless on the server by other projects,
> and we are a bout to de-couple the generic task/issue management API from
> Eclipse as well.
So it seems that the roadmap will be:
* Mylar project will provide 'Abstraction API' for and implementations for
various trackers;
* Maven wil use those libraries in plugins that will deal with trackers
right?
Or you're going to move 'generic task/issue mgmt API' out of Mylar,
to somewhere elese (Maven Issue projects/Codehaus ? :)
Regards,
Tomek
>
> It would be great to have Maven be a driver for that and we would be happy
> to package the API in a way that makes it easy for Maven to consume. To get
> started, would it suffice if we produced a JAR with a JRE 1.5 and
> org.eclipse.runtime dependency that provided you API for doing the
> following:
> 1) create a repository (e.g. bugzilla)
> 2) query the repository, get bugs back, check values
> 3) operate on one or more bugs (e.g. change milestones, submit)
>
> Mik
>
> --
> Mik Kersten, http://kerstens.org/mik
> Mylar Project Lead, http://eclipse.org/mylar
>
> > -----Original Message-----
> > From: Jason van Zyl [mailto:jason@maven.org]
> > Sent: Monday, July 03, 2006 11:05 AM
> > To: Maven Developers List
> > Cc: Mik Kersten
> > Subject: Re: Common API for issue tracking systems
> >
> > Hi,
> >
> > One person who should definitely be pulled into the discussion is Mik
> > Kersten. He's the fellow who works on Mylar and has integration for
> > Bugzilla and JIRA and I think Mantis. He's got some code that would
> > definitely be of use.
> >
> > Mik, are you interested creating a general library for issue
> > management here?
> >
> > Sorry for just pulling you in here but I figure it's just easier to
> > get you involved as the topic has come up :-)
> >
> > Jason.
> >
> > On 3 Jul 06, at 5:07 PM 3 Jul 06, Mark Hobson wrote:
> >
> > > Hi there,
> > >
> > > I was wondering whether any thought had been given to an abstract
> > > issue tracking API with implementations for Bugzilla, JIRA, etc.? I
> > > can see a couple of uses within maven:
> > >
> > > * Querying the issues fixed when releasing a new version of a project,
> > > to be used within the maven-changes-plugin
> > >
> > > * Creating a new version of a product in the underlying issue tracking
> > > system when releasing a new version of a project
> > >
> > > I couldn't see this abstraction in the maven-changes-plugin, but
> > > correct me if I'm wrong.
> > >
> > > I've recently written some code to programmatically manipulate
> > > Bugzilla, and thought this could be expanded into a general-purpose
> > > abstract API for manipulating issue tracking systems. Rather like
> > > Wagon is to transports and SCM is to SCMs.
> > >
> > > It'd be good to see Bugzilla support within maven and I'd be
> > > interested in people's thoughts.
> > >
> > > Cheers,
> > >
> > > Mark
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> > Jason van Zyl
> > jason@maven.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Brett Porter <br...@maven.org>.
This is cool to know. You may have missed it in the dev@ thread, but
Tomasz has also started this for Mantis and was hoping to contribute it
to the Maven library:
http://svn.sourceforge.net/viewcvs.cgi/itapi/project/trunk/
On 5/07/2006 6:24 AM, Mik Kersten wrote:
> It would be great to have Maven be a driver for that and we would be happy
> to package the API in a way that makes it easy for Maven to consume. To get
> started, would it suffice if we produced a JAR with a JRE 1.5 and
> org.eclipse.runtime dependency that provided you API for doing the
> following:
As far as Maven consuming it, that would work. JRE 5 is a higher
requirement than we currently have, but we can look at that. I assume
the eclipse runtime is just support code that will work outside of Eclipse?
The main concern in the long term would be the license. If it is at
Eclipse and under the EPL, then we will only be able to use it in binary
form - which means any modifications or adjustments for Maven will need
to go through Mylar.
Of course, I'm sure you would be more than welcome to bring the API to
Maven to work on as well!
> 1) create a repository (e.g. bugzilla)
> 2) query the repository, get bugs back, check values
> 3) operate on one or more bugs (e.g. change milestones, submit)
These sound great.
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Common API for issue tracking systems
Posted by Mik Kersten <be...@acm.org>.
Thanks for pulling me in Jason, this is good timing. In terms of Mylar's
'Connectors' we currently have a robust and well tested framework for
querying Bugzilla and JIRA. Trac will be ready for experimentation within a
week or so, and no, there is no Mantis connector yet. The Bugzilla
connector is already being used headless on the server by other projects,
and we are a bout to de-couple the generic task/issue management API from
Eclipse as well.
It would be great to have Maven be a driver for that and we would be happy
to package the API in a way that makes it easy for Maven to consume. To get
started, would it suffice if we produced a JAR with a JRE 1.5 and
org.eclipse.runtime dependency that provided you API for doing the
following:
1) create a repository (e.g. bugzilla)
2) query the repository, get bugs back, check values
3) operate on one or more bugs (e.g. change milestones, submit)
Mik
--
Mik Kersten, http://kerstens.org/mik
Mylar Project Lead, http://eclipse.org/mylar
> -----Original Message-----
> From: Jason van Zyl [mailto:jason@maven.org]
> Sent: Monday, July 03, 2006 11:05 AM
> To: Maven Developers List
> Cc: Mik Kersten
> Subject: Re: Common API for issue tracking systems
>
> Hi,
>
> One person who should definitely be pulled into the discussion is Mik
> Kersten. He's the fellow who works on Mylar and has integration for
> Bugzilla and JIRA and I think Mantis. He's got some code that would
> definitely be of use.
>
> Mik, are you interested creating a general library for issue
> management here?
>
> Sorry for just pulling you in here but I figure it's just easier to
> get you involved as the topic has come up :-)
>
> Jason.
>
> On 3 Jul 06, at 5:07 PM 3 Jul 06, Mark Hobson wrote:
>
> > Hi there,
> >
> > I was wondering whether any thought had been given to an abstract
> > issue tracking API with implementations for Bugzilla, JIRA, etc.? I
> > can see a couple of uses within maven:
> >
> > * Querying the issues fixed when releasing a new version of a project,
> > to be used within the maven-changes-plugin
> >
> > * Creating a new version of a product in the underlying issue tracking
> > system when releasing a new version of a project
> >
> > I couldn't see this abstraction in the maven-changes-plugin, but
> > correct me if I'm wrong.
> >
> > I've recently written some code to programmatically manipulate
> > Bugzilla, and thought this could be expanded into a general-purpose
> > abstract API for manipulating issue tracking systems. Rather like
> > Wagon is to transports and SCM is to SCMs.
> >
> > It'd be good to see Bugzilla support within maven and I'd be
> > interested in people's thoughts.
> >
> > Cheers,
> >
> > Mark
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> Jason van Zyl
> jason@maven.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Jason van Zyl <ja...@maven.org>.
Hi,
One person who should definitely be pulled into the discussion is Mik
Kersten. He's the fellow who works on Mylar and has integration for
Bugzilla and JIRA and I think Mantis. He's got some code that would
definitely be of use.
Mik, are you interested creating a general library for issue
management here?
Sorry for just pulling you in here but I figure it's just easier to
get you involved as the topic has come up :-)
Jason.
On 3 Jul 06, at 5:07 PM 3 Jul 06, Mark Hobson wrote:
> Hi there,
>
> I was wondering whether any thought had been given to an abstract
> issue tracking API with implementations for Bugzilla, JIRA, etc.? I
> can see a couple of uses within maven:
>
> * Querying the issues fixed when releasing a new version of a project,
> to be used within the maven-changes-plugin
>
> * Creating a new version of a product in the underlying issue tracking
> system when releasing a new version of a project
>
> I couldn't see this abstraction in the maven-changes-plugin, but
> correct me if I'm wrong.
>
> I've recently written some code to programmatically manipulate
> Bugzilla, and thought this could be expanded into a general-purpose
> abstract API for manipulating issue tracking systems. Rather like
> Wagon is to transports and SCM is to SCMs.
>
> It'd be good to see Bugzilla support within maven and I'd be
> interested in people's thoughts.
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Jason van Zyl
jason@maven.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by David Blevins <da...@visi.com>.
A bit ago a created a client for Jira which may be useful:
http://docs.codehaus.org/display/SWIZZLE/Swizzle+Jira
http://swizzle.codehaus.org/swizzle-jira/
-David
On Jul 3, 2006, at 9:17 AM, Vincent Massol wrote:
> +1. Actually I thought there was already a project for this but I was
> probably anticipating...
>
> * SCM for SCMs
> * Wagon for transports
> * Cargo for containers
>
> ... Spoor for bug trackers (or whatever other name!)
>
> -Vincent
>
>> -----Original Message-----
>> From: Mark Hobson [mailto:markhobson@gmail.com]
>> Sent: lundi 3 juillet 2006 18:08
>> To: Maven Developers List
>> Subject: Common API for issue tracking systems
>>
>> Hi there,
>>
>> I was wondering whether any thought had been given to an abstract
>> issue tracking API with implementations for Bugzilla, JIRA, etc.? I
>> can see a couple of uses within maven:
>>
>> * Querying the issues fixed when releasing a new version of a
>> project,
>> to be used within the maven-changes-plugin
>>
>> * Creating a new version of a product in the underlying issue
>> tracking
>> system when releasing a new version of a project
>>
>> I couldn't see this abstraction in the maven-changes-plugin, but
>> correct me if I'm wrong.
>>
>> I've recently written some code to programmatically manipulate
>> Bugzilla, and thought this could be expanded into a general-purpose
>> abstract API for manipulating issue tracking systems. Rather like
>> Wagon is to transports and SCM is to SCMs.
>>
>> It'd be good to see Bugzilla support within maven and I'd be
>> interested in people's thoughts.
>>
>> Cheers,
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
>
> ______________________________________________________________________
> _____
> Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et
> son interface révolutionnaire.
> http://fr.mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Jason van Zyl <ja...@maven.org>.
On 4 Jul 06, at 11:16 AM 4 Jul 06, Steve Loughran wrote:
> Vincent Massol wrote:
>> +1. Actually I thought there was already a project for this but I was
>> probably anticipating...
>> * SCM for SCMs
>> * Wagon for transports
>> * Cargo for containers
>> ... Spoor for bug trackers (or whatever other name!)
>> -Vincent
>
> very +1 too, though I'd like it decoupled from any partiucular
> build tool if possible, primarily because you can do other things
> outside the build itself. Imagine apps auto-opening bugreps on
> system crashes, for example.
>
What we have currently is not coupled to Maven just as MavenSCM and
MavenWagon aren't aside from the "Maven" name in there.
> see also some thoughts on cross-system defect linking; everything
> should have a URL:
> http://www.1060.org/blogxter/entry?
> publicid=4D798FF1B0235EDEFA40B58CC6FD2697
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Jason van Zyl
jason@maven.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by jerome lacoste <je...@gmail.com>.
On 7/5/06, Steve Loughran <st...@apache.org> wrote:
> Jochen Wiedmann wrote:
> > On 7/4/06, Steve Loughran <st...@apache.org> wrote:
> >
> >> That'll be the ant-that-has-to-support-java-1.2 on
> >> everything-and-build-with-no-dependencies, won't it?
> >
> > Be that as it may, but personally I prefer this over the
> > maven-which-needs-thousands-of-jars-from-codehaus-for-whatever
> > approach... :-)
> >
>
> The problem with Ant's approach is that there is some very useful stuff
> there; <exec> is how java's process stuff should work, <java> is almost
> a substitute for the JRE not implementing fork() (presumably as they
> couldnt find it in the win32 API), and yet reuse of that stuff is mostly
> denied to everyone unless they include ant.jar, create their own project
> and execute a Task in the project instance just created. So while the
> tight coupling is good for ant, it stops people downstream from using it
> self contained. You see this with things like cargo, tomcat, weblogic
> all having to include an ant jar just to exec stuff. The convenience of
> absolute integration and zero dependencies is achieved at the expense of
> reusability.
Slightly related...
There ve been talk to make a separate commons-exec library to let
people do execution easily. I tried to help, but I didn't get time to
clean up my submission back last year in October. Thought about it
again this morning under my shower :)
May have more time this summer. See the commons-dev archives. Feel free to ask.
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Steve Loughran <st...@apache.org>.
Jochen Wiedmann wrote:
> On 7/4/06, Steve Loughran <st...@apache.org> wrote:
>
>> That'll be the ant-that-has-to-support-java-1.2 on
>> everything-and-build-with-no-dependencies, won't it?
>
> Be that as it may, but personally I prefer this over the
> maven-which-needs-thousands-of-jars-from-codehaus-for-whatever
> approach... :-)
>
The problem with Ant's approach is that there is some very useful stuff
there; <exec> is how java's process stuff should work, <java> is almost
a substitute for the JRE not implementing fork() (presumably as they
couldnt find it in the win32 API), and yet reuse of that stuff is mostly
denied to everyone unless they include ant.jar, create their own project
and execute a Task in the project instance just created. So while the
tight coupling is good for ant, it stops people downstream from using it
self contained. You see this with things like cargo, tomcat, weblogic
all having to include an ant jar just to exec stuff. The convenience of
absolute integration and zero dependencies is achieved at the expense of
reusability.
-s.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Jochen Wiedmann <jo...@gmail.com>.
On 7/4/06, Steve Loughran <st...@apache.org> wrote:
> That'll be the ant-that-has-to-support-java-1.2 on
> everything-and-build-with-no-dependencies, won't it?
Be that as it may, but personally I prefer this over the
maven-which-needs-thousands-of-jars-from-codehaus-for-whatever
approach... :-)
--
Whenever you find yourself on the side of the
majority, it is time to pause and reflect.
(Mark Twain)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Steve Loughran <st...@apache.org>.
Brett Porter wrote:
> On 4/07/2006 8:16 PM, Steve Loughran wrote:
>> very +1 too, though I'd like it decoupled from any partiucular build
>> tool if possible, primarily because you can do other things outside
>> the build itself. Imagine apps auto-opening bugreps on system crashes,
>> for example.
>
> None of the shared libraries (be it wagon, scm, doxia, issue, jxr, the
> repository tools, etc) are coupled to a particular build tool. It's only
> Ant that does that :)
:)
That'll be the ant-that-has-to-support-java-1.2 on
everything-and-build-with-no-dependencies, won't it?
we have our own exec logic in smartfrog BTW. There's no need for most
programs to have logic that handles execution of java programs on
netware, or the correct handling of error codes on VMS, not unless they
have to, and it makes the interior of the exec and java classes in Ant
kind of messy. Worse yet, you have to deal with support calls related to
Netware filesystems, VMS [1]or obscure IBM mainframes [2]. You do not
want to go there. It is bad enough having to keep win98 vmware images
around.
[1] http://issues.apache.org/bugzilla/show_bug.cgi?id=31589
[2] http://issues.apache.org/bugzilla/show_bug.cgi?id=28111
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Tomasz Pik <to...@gmail.com>.
On 7/4/06, Brett Porter <br...@apache.org> wrote:
> On 4/07/2006 8:16 PM, Steve Loughran wrote:
> > very +1 too, though I'd like it decoupled from any partiucular build
> > tool if possible, primarily because you can do other things outside the
> > build itself. Imagine apps auto-opening bugreps on system crashes, for
> > example.
>
> None of the shared libraries (be it wagon, scm, doxia, issue, jxr, the
> repository tools, etc) are coupled to a particular build tool. It's only
> Ant that does that :)
>
> Just flicking through it, there doesn't seem to be much there for the
> issue stuff but I know that a couple of people have a keen interest
> here, and there is code in the changes plugin, and some ruby code that
> possibly does a bit more.
>
> http://svn.apache.org/viewvc/maven/sandbox/issue/
And here: http://svn.sourceforge.net/viewcvs.cgi/itapi/project/trunk/
is a kind of 'issue tracker' abstracton and working client for mantis
(which has creating new issue and some report possibility).
I'd like to contubute this in some way to maen issue project.
Regards,
Tomek
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Brett Porter <br...@apache.org>.
On 4/07/2006 8:16 PM, Steve Loughran wrote:
> very +1 too, though I'd like it decoupled from any partiucular build
> tool if possible, primarily because you can do other things outside the
> build itself. Imagine apps auto-opening bugreps on system crashes, for
> example.
None of the shared libraries (be it wagon, scm, doxia, issue, jxr, the
repository tools, etc) are coupled to a particular build tool. It's only
Ant that does that :)
Just flicking through it, there doesn't seem to be much there for the
issue stuff but I know that a couple of people have a keen interest
here, and there is code in the changes plugin, and some ruby code that
possibly does a bit more.
http://svn.apache.org/viewvc/maven/sandbox/issue/
Cheers,
Brett
--
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Mark Hobson <ma...@gmail.com>.
On 04/07/06, Steve Loughran <st...@apache.org> wrote:
> very +1 too, though I'd like it decoupled from any partiucular build
> tool if possible, primarily because you can do other things outside the
> build itself. Imagine apps auto-opening bugreps on system crashes, for
> example.
I agree, and this is exactly what my bugzilla code is used for at the
moment - when a system crashes it files a bug report with a crash
report attached in bugzilla.
It'd be good to see a shared project providing this abstraction that
could be used by maven, mylar and other projects like mine.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Common API for issue tracking systems
Posted by Steve Loughran <st...@apache.org>.
Vincent Massol wrote:
> +1. Actually I thought there was already a project for this but I was
> probably anticipating...
>
> * SCM for SCMs
> * Wagon for transports
> * Cargo for containers
>
> ... Spoor for bug trackers (or whatever other name!)
>
> -Vincent
very +1 too, though I'd like it decoupled from any partiucular build
tool if possible, primarily because you can do other things outside the
build itself. Imagine apps auto-opening bugreps on system crashes, for
example.
see also some thoughts on cross-system defect linking; everything should
have a URL:
http://www.1060.org/blogxter/entry?publicid=4D798FF1B0235EDEFA40B58CC6FD2697
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Common API for issue tracking systems
Posted by Vincent Massol <vi...@massol.net>.
+1. Actually I thought there was already a project for this but I was
probably anticipating...
* SCM for SCMs
* Wagon for transports
* Cargo for containers
... Spoor for bug trackers (or whatever other name!)
-Vincent
> -----Original Message-----
> From: Mark Hobson [mailto:markhobson@gmail.com]
> Sent: lundi 3 juillet 2006 18:08
> To: Maven Developers List
> Subject: Common API for issue tracking systems
>
> Hi there,
>
> I was wondering whether any thought had been given to an abstract
> issue tracking API with implementations for Bugzilla, JIRA, etc.? I
> can see a couple of uses within maven:
>
> * Querying the issues fixed when releasing a new version of a project,
> to be used within the maven-changes-plugin
>
> * Creating a new version of a product in the underlying issue tracking
> system when releasing a new version of a project
>
> I couldn't see this abstraction in the maven-changes-plugin, but
> correct me if I'm wrong.
>
> I've recently written some code to programmatically manipulate
> Bugzilla, and thought this could be expanded into a general-purpose
> abstract API for manipulating issue tracking systems. Rather like
> Wagon is to transports and SCM is to SCMs.
>
> It'd be good to see Bugzilla support within maven and I'd be
> interested in people's thoughts.
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org