- 1 Orbit FAQ
- 1.1 What is Orbit?
- 1.2 Does Orbit replace or affect the Eclipse Foundation legal process?
- 1.3 If a library is approved for use in "all" projects, do I still have to go through the legal process?
- 1.4 Do projects have to use the Orbit bundles?
- 1.5 What if I don't want to put the library I need into Orbit?
- 1.6 Who are the committers in Orbit?
- 1.7 How do I become a committer in Orbit?
- 1.8 Which libraries are managed in Orbit
- 1.9 How does Orbit manage multiple versions of the same library?
- 1.10 How is source managed/delivered?
What is Orbit?
Orbit is a project designed to be a repository for third party libraries that are approved for use in Eclipse projects. If the incoming libraries are not already bundles then Orbit committers will work to create a bundle that is suitable for use in Eclipse projects.
Does Orbit replace or affect the Eclipse Foundation legal process?
NO! Orbit holds only libraries that have been approved by the standard legal process. Projects must still follow this process to request permission to use libraries in their releases.
If a library is approved for use in "all" projects, do I still have to go through the legal process?
As of this writing, all projects must request permission to use any third party libraries. More generally, this is a question for the legal team. Orbit does not affect the IP policy and legal process.
Do projects have to use the Orbit bundles?
This is not explicitly required however we do hope that the Release Review process is enhanced to require justification for using a library in your release and not using the corresponding bundle from Orbit. There may well be valid scenarios here the Orbit bundle is not appropriate but projects are strongly urged to share as much as possible.
What if I don't want to put the library I need into Orbit?
That's fine but you will be foregoing the help and support you would get of the greater Orbit community as well as preventing others from sharing in your efforts. Keep in mind that you may have to justify this approach when it comes time for your release review.
Who are the committers in Orbit?
The following is the current list of committers and the projects they represent. Note that those with ?? after their names are potential committers.
|Jeff McAffer (Project Lead)||Eclipse|
How do I become a committer in Orbit?
Orbit committers are generally committers from other Eclipse projects that have a need for a third party library. These people come to Orbit with an approved library and propose to include it in Orbit. If they are not already a committer and their project does not have any committers, they can become a committer by agreeing to bundle and maintain the new library. Accordingly, they will then be responsible for the care and feeding of that library and the corresponding bundle.
Which libraries are managed in Orbit
The complete list is of bundles available from Orbit is on the Orbit download page. As the project is just getting underway, we don't have a downloads page so here is a list of the bundles that will be included in Orbit.
|Batik PDF||org.apache.batik.pdf||1.0 beta2|
|OSGi services API||org.eclipse.osgi.services||3.1.100|
|Servlet API||org.eclipse.equinox.servlet.api||2.3 and 2.4|
How does Orbit manage multiple versions of the same library?
Luckily OSGi supports multiple versions of the same bundle installed and running at the same time so this does not present any particular runtime problems. At development time however there is a challenge of project naming. Since the Eclipse convention has been to use the bundle symbolic name as the name of the project, there would be a conflict if two versions of the same project need to be in the workspace at the same time. We still need to weigh the options here.
How is source managed/delivered?