This page provides the required docuware for the Object Teams 2.1.0 Release Review, as part of the upcoming Juno Simultaneous Release.
See also bug 380760
The Object Teams Project provides tooling for developing highly modular evolvable software using the language OT/J
- compiler and runtime for OT/J based on the JDT compiler
- comprehensive IDE for OT/J based on the JDT
- extension for executing OT/J code within Equinox
New in this release
- New and Noteworthy is available at http://www.eclipse.org/objectteams/pages/new_in_2.1.html
- Lifting in call hierarchy
- Content Assist
- Add signatures to method binding
- Implement abstract methods from implicit super role
- Improved handling of base imports
- Basic code formatting for OT/J
- Java 7 support
- @Override for static role methods
- Base class as method return
- Run / Debug
- Simplified launching with OT/Equinox
- Hot code replacement
- Report multiple callins
- Object Teams Runtime Environment
- Memory optimization
- Performance optimization
- Release Engineering
- Source bundles
- Documentation hosted at http://www.eclipse.org/objectteams/documentation.php
- During the Juno cycle the Object Teams project has migrated from SVN to Git.
This release brings no breaking API changes.
- The project lead certifies that the requirements for Eclipse Quality APIs have been met for this release.
- API Tooling has been employed.
- The help plug-in has been split to separate code from help pages.
- The OTDT works with Eclipse 4.2 and 3.8 alike
- No branching needed
- Continued improvements, and adoption of upstream improvements.
Nothing has been deprecated.
- 90 bugs fixed in the Juno cycle
- only marginal increase of open bugs from 39 to 44
- No standard exists for OT/J, the project provides the only implementation for this technology
- Language definition (OTJLD) is maintained at objectteams.org.
- Version 1.3 has been frozen as the basis for the OTDT 2.0.0+
- OT/J is executed on a standard Java virtual machine
- OT/Equinox runs on the Equinox framework using ...
- only standard OSGi headers in MANIFEST.MF
- only regular extensions in plugin.xml
- AdapterHooks as supported by Equinox
- Installing the OTDT (and any OT/Equinox appl.)
- using only existing p2 mechanisms
Continuous small improvements.
Object Teams is a “+2” component in the simultaneous release. All milestones have been announced on the day of the corresponding Juno milestone.
- Interaction in Bugzilla
- Activity on the Object Teams newsgroup
- 6 (comprehensive) blog posts on Object Teams since the 2.0.0 release
- blog is integrated on planet.eclipse.org and features Object Teams as well as JDT/Core work
- Tight integration with the JDT team
- JDT's support for null annotations has been prototyped using Object Teams
- Several bugs in JDT found during work on Object Teams
- All improvements in the JDT are promptly adopted in Object Teams
- Object Teams was featured in these presentations:
- “Bye, bye, NPE” at EclipseCon Europe'11
- JDT Tutorial at EclipseCON'12
The Object Teams component leadership verifies that:
- the about files and use licenses are in place as per the Guidelines to Legal Documentation.
- all contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
- all significant contributions have been reviewed by the Foundation's legal staff.
- all non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff.
- all Contribution Questionnaires have been completed.
- the "provider" field of each plug-in is set to "Eclipse.org - Object Teams“.
- the "copyright" field of each feature is set to the copyright owner (the Eclipse Foundation is rarely the copyright owner).
- any third-party logos or trademarks included in the distribution (icons, help file logos, etc) have been licensed under the EPL.
- any fonts or similar third-party images included in the distribution (e.g. in PDF or EPS files) have been licensed under the EPL.
The approved IP log for the Object Teams Project is attached in bugzilla at https://bugs.eclipse.org/bugs/attachment.cgi?id=216610
Release Train Participation
The Eclipse Object Teams Project has contributed on time to all Juno milestones.
No issues were detected in the Software Repository Reports of the simultaneous release.
The current project plan is available from http://www.eclipse.org/projects/project-plan.php?projectid=tools.objectteams
A new byte code weaver was planned for the 2.1 release. While good progress has been made on this component, the integration into the OTDT has to be postponed for 2.2 (also pending the move of some code to Eclipse.org).
A major work package both in JDT and Object Teams during the Kepler cycle will be the implementation/integration of support for Java 8.
A development plan for the 2.1 release is not yet available.