Skip to main content
Jump to: navigation, search

Difference between revisions of "Developer Team Page"

Line 31: Line 31:
* List of [[Higgins Third Party_Dependencies]]
* List of [[Higgins Third Party Dependencies]]
* [    Open Higgins Ipzilla items] (committers only)
* [    Open Higgins Ipzilla items] (committers only)
* [[Response to Open Specification Promise]] --Higgins and Microsoft CardsSpace
* [[Response to Open Specification Promise]] --Higgins and Microsoft CardsSpace

Revision as of 15:44, 20 December 2007

Note: This page is relevant only for Higgins committers and active contributors.

Repository Branch Structure

  • HEAD -- ongoing development for Higgins 1.0
  • B1-0M9 -- state of components at the end of 1.0M9
  • M0-8 -- state of components at the end 1.0M8

Meetings and Events


Coding Standards

  • Coding-related Conventions
  • All Java code must build using JRE 1.4 (and must support both Sun and IBM JREs)

Misc Tools




Contributions by team members

Eclipse Foundation-related Info

Eclipse Committers



Clarification of IP processes for use of third party libraries

  • Any time anyone working on the Higgins project wants to introduce a project dependency, it needs to be brought forward to the Higgins project.
  • If the decision is made to introduce the dependency and the dependency involves software that is not licensed under the EPL, then a formal IP process needs to be gone though to approve the software binaries for inclusion in the project cvs. Note that this process must be followed even if the software is a common java library used by other Eclipse processes. (If the software has been used by another Eclipse project, the process is much faster.) Eclipse has a system IPzilla for managing this process. If you are anticipating a dependency, you need to bring it forward as soon as possible to allow time for the IP due diligence process to take place. See more about IPzilla below.
  • Libraries licensed with EPL are the easiest to get permission to use, followed by Apache 2.0. GPL and LGPL licences are not compatible with EPL.


  • Orbit is 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. See for a list or Orbit managed libraries. Orbit managed libaries are the easiest of third party libraries to add to an Eclipse project. Even if a library is listed under Orbit, you still need to go through the IPzilla process before putting it into the Higgins CVS.


Back to the top