Re: [cbi-dev] An "Eclipse central repository"

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

This is inaccurate. It is true that p2 uses version ranges,
but it is quite possible to specify a range that specifies an exact match
that only one version can satisfy. Most Eclipse applications are built
using Eclipse "features", and feature inclusion dependencies
map to exactly one version in p2. The Eclipse SDK and likely many other
projects will install predictably from a p2 repository regardless of how
that repository changes over time (assuming the exact versions listed in
the feature aren't removed of course).

John

Igor Fedorenko wrote on 04/04/2012 12:26:10 PM:

> This won't work because P2 (and OSGi in general) use dependency version
> ranges almost exclusively, where vast majority of Maven projects use
> specific dependency versions. Single P2 repository will result in
> virtually unpredictable installation and/or build results as new
> versions are deployed to the repository.
> 
> --
> Regards,
> Igor
> 
> On 12-04-04 11:51 AM, Mickael Istria wrote:
> > Hi again,
> >
> > What makes Maven great is that everything is available through
a "Maven
> > central repository". It is pretty easy to find a dependency.
> > What about setting up an "Eclipse central repository"
where all releases
> > of all project could push their bits?
> > It would ensure that Eclipse.org keeps an archive of everything
that has
> > been produced, and it would be a good entry point for most Eclipse
> > consumers. It is "just" a step to add to the release
process: "When
> > releasing a project, you have to ask your new release repositories
to be
> > merged into the central repository".
> >
> > Regards,
> > --
> > Mickael Istria
> > Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
> > My blog <http://mickaelistria.wordpress.com>
- My Tweets
> > <http://twitter.com/mickaelistria>