Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of mkleint@gmail.com designates
 64.233.182.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Xv1HyFryYd0GrenhsMfklpBNLSKQGH1mAnv/HS8HWVcC4Y1yqzWgWfqDIuos0APtXCH1DSrMXt6snwDlUlWPmolzU1WqmzcpT5P/ETij7pF/86i4MGlXGMFDfhXzMI9WR7uf4Hkgt4RLxfq7P1H0mxhAJ+Ob0A1NEv+5zRxH+Zo=
Message-ID: <f84708e90607062211m4bb3ed23o218dd8c105bfce57@mail.gmail.com>
Date: Fri, 7 Jul 2006 07:11:12 +0200
From: "Milos Kleint" <mkleint@gmail.com>
To: "Maven Developers List" <dev@maven.apache.org>
Subject: Re: Common API for issue tracking systems
In-Reply-To: <012a01c6a159$b5b30f10$6700a8c0@beatmik>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <cda784f10607060018l80fad99j636a99b8d00e2303@mail.gmail.com>
	 <012a01c6a159$b5b30f10$6700a8c0@beatmik>

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 <beatmik@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