RE: [egit-dev] JGit projection creatoin?

["Mik Kersten" <mik@xxxxxxxxxxx>]

I was just pointing out that we would stray from what had been a convention
that had previously been put in place by Platform, that some other projects
have followed (eg, Mylyn has org.eclipse.mylyn.team.* APIs for CVS/SVN
change set management).  But to be clear I'd like to throw in my "-1" for
using "team" in the package segment.

I do think it is relevant to consider using a single namespace for the
project, eg, org.eclipse.egit, and having the "jgit" stuff under that.
While transparent to users, it is relevant to developers and contributors,
who are often forced to browse very long alphabetically sorted lists of
bundle names (eg, in the Package Explorer, Plug-in tab of the launch
configuration wizard).  "org.eclipse.jgit" would be separated from
"org.eclipse.egit" by a large number of bundles in such listings.

Mik

> -----Original Message-----
> From: Alex Blewitt [mailto:alex.blewitt@xxxxxxxxx]
> Sent: September-25-09 10:51 AM
> To: mik.kersten@xxxxxxxxxxx; EGit developer discussion
> Cc: EGit developer discussion
> Subject: Re: [egit-dev] JGit projection creatoin?
> 
> On 25 Sep 2009, at 17:38, "Mik Kersten" <mik@xxxxxxxxxxx> wrote:
> 
> > It may also make sense to follow the Platform convention of using
> > the "team"
> > namespace.
> 
> Actually, that's for the platform project's team component. Given that
> there is a "team" component in e.g. Bugzilla as well, this may
> ultimately confuse users as to where to report bugs. So given that (e)
> git is its own top level project, using org.eclipse.(e)git seems
> reasonable (though I concur with the separate ui and non ui plugins
> which I believe there are already.
> 
> If JGit ends up being its own top level project then
> org.eclipse.jgit.* and org.eclipse.egit.* probably makes sense. If
> not, org.eclipse.(e)git.egit and org.eclipse.(e)git.jgit might be
> better.
> 
> Alex