Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
From: "Mik Kersten" <beatmik@acm.org>
To: "'Jason van Zyl'" <jason@maven.org>,
        "'Maven Developers List'" <dev@maven.apache.org>
Subject: RE: Common API for issue tracking systems
Date: Tue, 4 Jul 2006 13:24:06 -0700
Message-ID: <000e01c69fa7$ce049740$06000100@beatmik>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acaeyza0iAHrpf+tScmqdxy0HgNihAA0Z3Iw
In-Reply-To: <199C2496-A19D-4B0F-8DAA-4C921752B6C7@maven.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