Developer Team Page
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-related Conventions
- All Java code must build using JRE 1.4 (and must support both Sun and IBM JREs)
- Generating anonymous psf file using PERL script --steps to generate anonymous psf file for a project including all it's dependencies
- Higgins2Ant -- new page, needs work
- Build Enhancements --wishlist of enhancements to the nightly and developer build processes
- Automated Builds --description of the existing nightly build process
- Starting a Higgins Build --how to kick off a build on the eclipse build server
- Copying necessary 3rd party libs to project lib folder using PERL script --steps to copy all necessary 3rd party libs from centralized location (local) to project lib folder
- Deployment Requirements -- gathering requirements for our build/deploy processes
- List of Higgins Third Party_Dependencies
- Open Higgins Ipzilla items (committers only)
- Response to Open Specification Promise --Higgins and Microsoft CardsSpace
- Draft Response to Open Specification Promise --earlier draft
Contributions by team members
- Higgins committers with contributions active in the 1.0 repository --Eclipse Legal Review
- Higgins developers with contributions active in the 1.0 repository --Eclipse Legal Review
- Development Resources
- Eclipse Development Process 2006 Revision Final
- Guide to the Eclipse Legal Documents
- Eclipse Committer Due Diligence Guidelines, feel free to email email@example.com with any IP related licensing or process questions
- Eclipse Legal Copyright standards
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 http://www.eclipse.org/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 http://wiki.eclipse.org/index.php/Orbit_Faq 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.