Re: [science-iwg] JDistlib

[Matthew Webber <matthew@xxxxxxxxxxxxxx>]

Isn't Eclipse Marketplace just aimed at providing a location to install features into a running p2-aware Eclipse application from? This is different from developers needing a way of getting binary artifacts (.jars) into their workspace (using Maven, Buckminster, Gradle, or your favourite build tool).

In addition to providing components that have been IP checked to a certain standard, Orbit also:

* provides a stable set of p2 sites

* for packages where the upstream provider has not included OSGI bundle information, Orbit provides a repackaged jar with the required OSGI headers in the manifest, so it can be published on the Orbit p2 site

These benefits are incredibly useful. There have been multiple attempts to provide such a resource (minus the IP checks). Examples:

(1) SpringSource Enterprise Bundle Repository http://ebr.springsource.com/repository/app/
" Here you'll find OSGi-ready versions of hundreds of open source enterprise libraries that are commonly used when developing Spring applications"

No longer maintained

(2) Eclipse Bundle Recipes https://projects.eclipse.org/projects/rt.ebr was supposed to take over from EBR, but itself appears to be dying

(3) http://central.sonatype.org/

(4) http://mvnrepository.com/

FWIW

Matthew

On 16 September 2015 at 15:22, Jay Jay Billings <jayjaybillings@xxxxxxxxx> wrote:

 (snip)

That being said, I really think we are going to have a rough way of it if we try to get every package that we work with dual licensed and/or into Orbit. I get the distinct feeling that we (the Group) seem to be the only people who think that is a good idea. So, instead, I think we should take advantage of WORKS-WITH dependencies and the Eclipse Marketplace. We've been discussing this on the Steering Committee calls and I have been looking into it. I am also in the process of reconfiguring a machine at ORNL to host the bits, eclipseice.ornl.gov (we can change the name if needed).

(snip)