Difference between revisions of "OTIndigo"

From Eclipsepedia

Jump to: navigation, search
m (Do No Harm)
(Unit Tests)
Line 120: Line 120:
  
 
===Unit Tests===
 
===Unit Tests===
* [[Image:Ok_green.gif]] currently more than 45400 tests
+
* [[Image:Ok_green.gif]] currently more than 51000 tests
 
** [[Image:Glass.gif]] publish test results?
 
** [[Image:Glass.gif]] publish test results?
  

Revision as of 16:14, 4 March 2011


The Eclipse Object Teams Project joined the Indigo release train. Here are the details wrt the Eclipse Simultaneous Release document. This page overlaps with [1] which is generated from the data entered through the portal, but here we give more information on background and details.

Contents

Do the basics ... early

  • Ok green.gif express statement of intent in the Portal

Planning

  • Ok green.gif update project plan

IP Documentation

  • Progress.gif ongoing

Release Review

  • (typically at RC2)

Play well with others ... to be in common repository

Communication

  • Ok green.gif subscribe to cross-project mailing list (sherrmann)
  • Ok green.gif subscribe to cross-project bugzilla inbox (sherrmann)
  • Ok green.gif provide contact details for build engineer (see objectteams.b3aggrcon).

API

Here is where the fun starts :)

  • Progress.gif document non-standard usage:
    • OTDT/NonAPI
    • patch feature for org.eclipse.jdt.core, approved as an exception by the Eclipse PMC, see this post and its replies.
  • Progress.gif Eclipse-wide strategy for dealing with all kinds of exceptions
  • Glass.gif further discussion (process & technology)
    • API requests in bugzilla
    • extended friend mechanisms?
      • integrate with API tools?
      • establish communication protocol between teams?

Message Bundles

  • Ok green.gif done.

Version Numbers

  • Ok green.gif 4-part version numbers are consistently used

OSGi bundle format

  • Ok green.gif all plugins are true OSGi bundles.

Execution Environment

  • Ok green.gif all bundles have BREE set to J2SE-1.5

Signing

  • Ok green.gif all jars are signed on build.eclipse.org

Jarred Bundles

  • Ok green.gif most bundles are jarred
    • some bundles required some tweaking during the 0.8 cycle:
      • Ok green.gif otdt: changing to jarred install worked out of the box
      • Ok green.gif otdt.ui.help: got it to work with the little patch in bug 329806
    • one bundle still requires unpack=false for technical reasons:
      • Unsupport.gif otdt.samples: could not be persuaded, the pde.ui.samples extension point doesn't work off a jarred plug-in.
      I filed bug 332748 to track this last reason for unpacking.

Re-use and share

  • Ok green.gif the only external dependency org.apache.bcel is consumed from Orbit.

Capabilities

Support Translations

  • Progress.gif string externalization is done, participation in babel initiated, waiting for our project to appear in the translation tool.

Excel in NL support

  • Ok green.gif the only relevant class was java.text.MessageFormat, which has been fully replaced by org.eclipse.osgi.util.NLS.

Branding

  • Ok green.gif About dialog icon with details is in place.

Do No Harm

  • Glass.gif 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.
    • before the fix for bug 329784 p2 touchpoints didn't support smooth installation of several plug-ins using adaptor hooks.
    Ok green.gif The bug has been resolved and was adopted in rev. 1373 for OTDT builds > 20110303.
    • OTDT's aspect bindings interfering with other features. Shouldn't happen, if it happens we can fix on short notice.
  • Glass.gif 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

  • Ok green.gif Builds ≥ 20110228 consistently use the February 1, 2011 version of the license text.

Be a good Eclipse Citizen ... and document it

Engage Community

  • Ok green.gif New&Noteworthy documents are available at each milestone (cumulative up-to release)

Usability

  • Ok green.gif Mimic and extend JDT's lead.

Performance

  • todo

Test Localization

  • todo

Enable Use with All Languages

  • todo awaiting users from non-western locals for input

Builds

Ramp Down Planned and Defined

  • todo

Accessibility

  • todo

Unit Tests

  • Ok green.gif currently more than 51000 tests
    • Glass.gif publish test results?

API Policy

  • Progress.gif will follow general rules concerning x-internal etc.

Retention Policy

  • todo

Project Metrics

  • Progress.gif docuware from 0.7.0 release revies should be a good starting point

Technical Details of Contributing to Indigo

  • Ok green.gif 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
  • Ok green.gif 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
  • Ok green.gif Two issues were fixed during joining the aggregation build:
    • Our pack200 files were affected by incompatibility between JDK 5 & 6 (see bug 311469#6 ff.).
    • The platform filter of our fragment org.eclipse.objectteams.otequinox.sunjvm had a typo which was never reported (see bug 329984, bug 329985).