RE: [egit-dev] JGit projection creatoin?

["Mik Kersten" <mik@xxxxxxxxxxx>]

+1 to Doug’s point.  In addition each new project incurring significant administrative overhead, in all my experiences leaning towards unity with related projects/components eases collaboration.  I still regret making AspectJ and AJDT separate projects (first in Technology then moving both to Tools), and they have a similar relationships as JGit and EGit, ie, AspectJ is completely independent of AJDT and happily runs on the command line or within NetBeans.  But then so does the jdt.core compiler, which is very nicely separated from jdt.ui, and I think their model has worked better.

 

Mik

 

--

Dr. Mik Kersten

CEO: http://tasktop.com

Lead: http://eclipse.org/mylyn

Follow: http://twitter.com/mik_kersten

 

From: egit-dev-bounces@xxxxxxxxxxx [mailto:egit-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer
Sent: September-25-09 2:50 PM
To: EGit developer discussion
Subject: Re: [egit-dev] JGit projection creatoin?

 

On Fri, Sep 25, 2009 at 4:34 PM, Robin Rosenberg <robin.rosenberg@xxxxxxxxxx> wrote:

fredag 25 september 2009 17:48:04 skrev "Shawn O. Pearce" <spearce@xxxxxxxxxxx>:

> Now that JGit has been approved by the board, should we be hosting
> it under the EGit project, or submitting a creation review for a
> new Technology project called JGit?  Or something else entirely?

I sort of like it being a separate project, partly because JGit is completely
independent of EGit and to make the difference in licensing clearer.

If that amounts to a lot of extra administrative work, then no. Most of
the work will still be around processing contributions, I think.

Trust me. It's too much admin work. Single project, multiple components accomplishes what you need.
 

-- robin

_______________________________________________
egit-dev mailing list
egit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/egit-dev