Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
OTIndigo
The Eclipse Object Teams Project intends to join the Indigo release train.
Here are the details wrt the Eclipse Simultaneous Release document.
Contents
Do the basics ... early
Planning
IP Documentation
Release Review
- (typically at RC2)
Play well with others ... to be in common repository
Communication
- subscribe to cross-project mailing list (sherrmann)
- subscribe to cross-project bugzilla inbox (sherrmann)
- provide contact details for build engineer (see objectteams.b3aggrcon).
API
Here is where the fun starts :)
- todo: document non-standard usage
- usage of internal classes
- aspect binding to bundle
- decapsulation
- interception
- patch feature for
org.eclipse.jdt.core
- Eclipse-wide strategy for dealing with all kinds of exceptions
- further discussion (process & technology)
- API requests in bugzilla
- extended friend mechanisms?
- integrate with API tools?
- establish communication protocol between teams?
Message Bundles
Version Numbers
OSGi bundle format
Execution Environment
Signing
Jarred Bundles
- most bundles are jarred
- check the following exceptions, is unpacking still needed?
- otdt: changing to jarred install seems to work out of the box, more testing needed
- otdt.ui.help: got it to work with the little patch in bug 329806
- otdt.samples: could be difficult to persuade the pde.ui.samples extension point to work off a jarred plug-in.
- I filed bug 332748 to track this last reason for unpacking.
- check the following exceptions, is unpacking still needed?
Capabilities
- todo
Support Translations
Excel in NL support
Branding
Do No Harm
- potential incompatibilities could arise from
- other feature providing a patch to
org.eclipse.jdt.core
, too. => incompatible - other feature applying bytecode weaving, too. Needs investigation, should be possible.
- actually p2 touchpoints don't currently support smooth installation of several plug-ins using adaptor hooks (see bug 329784).
- OTDT's aspect bindings interfering with other features. Shouldn't happen, if it happens we can fix on short notice.
- other feature providing a patch to
- planning to cross-test the OTDT with other bytecode weaving plugins installed
- These are not part of Indigo: AJDT, Greclipse, Scala IDE
- any weaving bundles in Indigo?
License text consistency
Be a good Eclipse Citizen ... and document it
Engage Community
- New&Noteworthy documents are available at each milestone (cumulative up-to release)
- e.g.: 0.7.0 N&N
Usability
Performance
- todo
Test Localization
- todo
Enable Use with All Languages
- todo awaiting users from non-western locals for input
Builds
- see OTBuilding
Ramp Down Planned and Defined
- todo
Accessibility
- todo
Unit Tests
API Policy
Retention Policy
- todo
Project Metrics
Technical Details of Contributing to Indigo
- As documented in OTBuilding the automated build includes creating a deployable p2 repository with these properties
- signed
- with pack200 files
- accumulative meta data per minor release
- categorized
- Our contribution has been committed by following the steps in Indigo/Contributing_to_Indigo_Build:
- We are contributing our features to the Programming Languages category, and OT/Equinox also to the EclipseRT Target Platform Components category, see objectteams.b3aggrcon
- Currently trying to resolve two issues of the aggregating build:
- Our pack200 files were broken, should be fixed (see bug 311469#6 ff.).
- The aggregator currently doesn't like our fragment org.eclipse.objectteams.otequinox.sunjvm (some issue relating to platform filters).