Skip to main content

[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 15:54, Shawn O. Pearce wrote:

AFAIK, all the jetty bundles are in Orbit. The p2 update site is here:

http://download.eclipse.org/tools/orbit/downloads/drops/R20090825191606/updateSite

Those are 6.1.x builds, and aren't in standard Eclipse workspaces
anyway.  Jetty moved to the Eclipse Foundation and has since released
a 7.x build.  I wanted to start with that version.

Jetty's 7.x builds are here:

http://download.eclipse.org/jetty/

<aside>

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.

Yes, I believe you're right. In fact, one of the problems with P2 update sites is that they are lots-of-little-sites rather than one big one, which is essentially the key to Maven. After all, anyone can publish their own Maven repo, but few do, because they upload it to one central repo.

In Eclipse's case, those repos are the result of the simultaneous releases, like the Helios update site and the like. But they're only really released once a year; whilst there are builds available for the milestones, they're not really coalesced into one update site.

But honestly, this isn't the only one of P2's problems. It's one of several. Ask yourself how many Eclipse developers actually use P2 to upgrade from one version to another in the milestone phase of any project ... (well, yes, the P2 guys do, to show it can be done, but that's probably telling in itself, right?)

The Eclipse Packaging project is really a symptom of the fact that there's no good update strategy. Worse, there's no shared stuff between builds (other than upstream) - so if you download the bits for a 32-bit Mac OS X RCP SDK, and you need to run on 64-bit Mac OS X RCP SDK, even though both can be delivered in one runtime/packging solution, you have to download the entire 160Mb again. Ask yourself how many copies of org.eclipse.osgi_xxx there are on any given Eclipse mirror, just from the released builds ...

Anyway, you're right that there's a lot of problems like this to solve. And Maven is certainly much, much better at it than P2 is. That's why I was excited about Tycho in restoring some kind of sense to the distribution of binaries; it solved both in one place.

Alex


Back to the top