The 2.1 release of EclispeLink will build upon the strong standards based solutions delivered in the 2.0.0 adding additional advanced functionality with ease of use and will address many of the community requests. Included in this are Milestone dates, and the development rampdown plan P2 Repository - These features are promoted to Helios on the +1 milestone dates. Complete ZIP file installer (eclispelink.jar) - Nightly downloads and test results Bundles ZIP file installer - Nightly downloads and test results Maven Repository - Usage Info The milestone and release candidate names align with the Helios. Milestone 5 - Available in Helios M5 on 02/05/2010 Milestone 6 - Available in Helios M6 on 03/19/2010 Milestone 7 - Available in Helios M7 on 05/07/2010 - For M7, EclipseLink plans to be functionally complete. The RCs following M7 will be used for bug fixes, packaging, and licensing issues Release Candidate 1 - Available in Helios RC1 on 05/21/2010 - Following RC1 project lead must approve code changes. Release Candidate 2 - Available in Helios RC2 on 05/28/2010 Release Candidate 3 - Available in Helios RC3 on 06/04/2010 - Only 'stop ship' issues fixed after RC3. Release Candidate 4 - Available in Helios RC4 on 06/11/2010 Eclipse Helios Release - including EclipseLink 2.1.0 EclipseLink is intended for use in most Java environments including: OSGi with specialized support for use with Equinox Java SE: Using the single eclipselink.jar or a combination of the bundles. Java EE: Using the single eclipselink.jar or a combination of the bundles. Web Containers: Using the single eclipselink.jar or a combination of the bundles. Spring: EclipseLink can be used directly or through the use of Spring's JPA templates. EclipseLink diagnostic messages are Localized, but no translated bundles are included in this release. EclispeLink is intended to be fully compatible with previous EclipseLink releases with the exception of previously deprecated API removed in this release. Please see Newly Deprecated API' and 'Removed API' below for complete details. This is the EclipseLink release that will go into the annual Eclipse release named Helios scheduled for release on June 23rd 2010. Some work will be required to ensure all of the release train requirements are met and that EclipseLink functions well within the IDE as well as within the RT platform. This work will include addressing better OSGi/Equinox compatibility. The last couple of release cycles have had a focus on major new feature areas (SDO, DBWS, JPA 2.0). This work has prevented the project team from keeping up with the community's request for enhancements and bug fixes. This release will endeavor to reduce the bug backlog to a more reasonable quantity. Continued improvements to usability focusing on simplified getting started steps as well as ability to find technical information on how EclipseLink works and how to solve both common and advanced requirements. The goal for this release is to address: Backlog of simple_fix bugs Backlog of submitted_patch bugs Reduce overall backlog of 'Future' bugs These are the bugs with Target Milestone = 2.1 and the Whiteboard entry includes 'Community' to identify the theme. The EclipseLink 2.1 release will include a new set of documentation delivered in HTML and PDF formats. This effort is based on these requirements. The goal is to improve the usability of the documentation. In this release the project is planning to increase the advanced features available through standard API using common extension points, custom annotations, and extended XML configuration files. The goal is to enable users to work with the standards (JPA, JAXB, SDO) as much as possible and simplify the usage of advanced features. Open Bugs: All , Foundation (Core) , JPA , MOXy , SDO , DBWS , Examples , Utils , Build Closed Bugs: All , Foundation (Core) , JPA , MOXy , SDO , DBWS , Examples , Utils , Build Additional Bug queries available here. The following APIs are newly deprecated in this release. Please update to the recommended replacement API. The following APIs have been removed in this release. These API were deprecated in earlier releases.