RE: [egit-dev] JGit projection creatoin?

["Mik Kersten" <mik@xxxxxxxxxxx>]

Sigh, that's always tricky.  Also, it could make sense to preserve the
"jgit" name if enough people are familiar with it.  One option would be just
to keep the "jgit" name and end up with something like:
* org.eclipse.egit.jgit
* org.eclipse.egit.core
* org.eclipse.egit.ui

Or you could consider the approach we've taken several times, mostly modeled
on Platform, to make the dependencies explicit in the bundle names:
* org.eclipse.egit.core (JGit stuff, runs happily on a Java classpath)
* org.eclipse.egit.resources (core stuff coupled to workspace/resources,
current stuff in core)
* org.eclipse.egit.ui (coupled to workbench/UI)

I'm not sure if "resources" is the right name there, but it could be
something along those lines.  Just fyi, my preference has been to minimize
the number of package segments, but other Eclipse projects take a more
hierarchical approach, eg:
* org.eclipse.egit.core.jgit
* org.eclipse.egit.core.resources
* org.eclipse.egit.ui..

Mik

> -----Original Message-----
> From: spearce@xxxxxxxxxxx [mailto:spearce@xxxxxxxxxxx]
> Sent: September-25-09 3:54 PM
> To: Mik Kersten
> Cc: 'EGit developer discussion'
> Subject: Re: [egit-dev] JGit projection creatoin?
> 
> Mik Kersten <mik@xxxxxxxxxxx> wrote:
> > +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.
> 
> The problem I can't resolve right now is the package namespace
> conflict on "egit.core".  If we make jgit egit.core, what do we do
> with the stuff that is in egit.core today?  That stuff that binds
> to the workspace and works in a headless environment?
> 
> --
> Shawn.