Re: [egit-dev] jgit and eclipse meta-data.

[Jason van Zyl <jason@xxxxxxxxx>]

On 2010-01-08, at 11:14 AM, Shawn O. Pearce wrote:

> Jason van Zyl <jason@xxxxxxxxx> wrote:
>> On 2010-01-08, at 10:54 AM, Shawn O. Pearce wrote:
>>> 
>>> I think a major failing of P2 is that there really isn't a great
>>> "P2 central" repository that bundles can be acquired from on demand.
>> 
>> This is not entirely true. We don't publicize it very much yet
>> but it does exist. It's more OSGi Central because we do P2 and OBR:
>> 
>> http://osgi.sonatype.org
> 
> This shouldn't have had to be done by Sonatype.  But its great that
> you are doing it.
> 

Well really who else is going to do it? Eclipse wants to be the center of the OSGi universe, Spring wants to be the center of the OSGi universe. Then we have the P2 versus OBR debate, then we have people using OSGi from Maven and and from other tools and most of the efforts are not overly collaborative.  So we're going to use the same framework we used for Maven and do it for OSGi. We don't care whether people want to do OSGi using Maven, P2, or OBR repositories. To some extent they will all exist for a while, if not indefinitely.

It will no longer be a question of whether to use the Spring bundle repository, or Orbit or Maven Central, or whatever. We can proxy and aggregate them all and no one else can do this right now. It's something that is unique to Nexus so that's why we're doing it.

> My point was, everyone keeps touting how great P2 is, and how great
> the P2 installer thingy is that is now in Eclipse 3.4 and later.
> But none of them thought we should also try to locate plugin
> dependencies on the fly the way Maven does.  (Or they did think
> about it and decided it wasn't worth the effort?  If so, WTF.)
> 
> Even if we had .project and META-INF/MANIFEST.MF files the way the
> Eclipse guys want... you can't just import the JGit test projects,
> because the workbench doesn't have the required bundles, and it
> doesn't know how to get them.  Even though the Eclipse IDE could have
> easily assumed it should check a repository hosted by eclipse.org,
> especially for eclipse.org projects.
> 
> No, we have to work around it with project set files, and importing
> more source code than we might otherwise need to.  Which is a
> massive bandaid.
> 
> I guess we should consider ourselves lucky that we also don't have to
> check out the source code for SWT in order to reference its packages?
> 
> *grumble grumble grumble*
> 
> -- 
> Shawn.
> _______________________________________________
> egit-dev mailing list
> egit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/egit-dev

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
----------------------------------------------------------