[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] jgit and eclipse meta-data.
|
On Jan 8, 2010, at 16:14, 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.
+1
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.
They do? I think it still sucks.
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.
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 think the idea of having to check out project set files isn't the
right way. What I would have done is to create an update site with a
JGit Dependencies feature, and made that available in the same place
that you can download JGit from. You don't (and shouldn't) need to
check out source for that, but you do need the bits in the local
runtime (either as a PDE platform target, or in your own installation).
Alex
