Project Plan For CDO Model Repository [CDO], version 4.1

Introduction

This document lays out the feature and API set for the third release of the CDO Model Repository Project (CDO), version 4.1. This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan.

Release Deliverables

The release deliverables have the same form as is found in most Eclipse projects, namely:
  • CDO Dawn Codegen EMF (Contains the code generation aspects for collaborative EMF support over CDO.)
  • CDO Dawn Codegen GMF (Contains the code generation aspects for collaborative GMF support over CDO.)
  • CDO Dawn Codegen (Contains the code generation aspects for graphical collaboration support over CDO.)
  • CDO Dawn Ecore Editor Extension (CDO Dawn Ecore Editor Extension contains bundles which enable the EMF Ecore Editor to work with CDO.)
  • CDO Dawn EcoreTools Diagram Extension (CDO Dawn EcoreTools Diagram Extension contains bundles which enable the EMF EcoreTools Diagram to work with CDO.)
  • CDO Dawn Examples (Contains example plugins to demonstrate a range of functions of Dawn.)
  • CDO Dawn Runtime (Contains the runtime aspects for graphical collaboration support over CDO.)
  • CDO Dawn SDK (Includes Runtime, Codegen, Tools, Examples, Documentation and Source.)
  • CDO Dawn Tests (Contains the CDO Dawn test plugins and sources. Ensure that SWTBot is already installed! Visit http://download.eclipse.org/technology/swtbot/helios/dev-build/update-site for a p2 repository that contains SWTBot.)
  • CDO Gastro Example (Contains the CDO Gastro RCP plugins, models and sources.)
  • CDO Model Repository Client (Contains the CDO client core and user interface plugins.)
  • CDO Model Repository Definitions (Contains the EMF-based definition and wiring plugins for CDO.)
  • CDO Model Repository Documentation (Contains the documentation of the CDO Model Repository.)
  • CDO Model Repository EPP (Contains a minimum CDO client and server environment for the Eclipse Modeling package.)
  • CDO Model Repository Examples Hibernate (Contains the CDO Hibernate example plugin and sources. Ensure that Hibernate is already installed! Visit http://www.elver.org/eclipse/2.0.0/update for a p2 repository that contains Hibernate.)
  • CDO Model Repository Examples (Contains the CDO example plugin, models and sources.)
  • CDO Model Repository Explorer Product (Contains the product definition of an installable CDO explorer.)
  • CDO Model Repository Migrator Tool (Contains the CDO Genmodel migrator/importer plugin.)
  • CDO Model Repository SDK (Includes Client, Server, Tools, Examples, Documentation and Source.)
  • CDO Model Repository Server DB4O (Contains the DB4O Store bundle. Ensure that DB4O Driver is already installed! Visit http://net4j.sourceforge.net/update for a p2 repository that contains DB4O Driver.)
  • CDO Model Repository Server DB (Contains the DBStore plugins.)
  • CDO Model Repository Server Hibernate (Contains the HibernateStore and Teneo integration plugins. Ensure that Hibernate is already installed! Visit http://www.elver.org/eclipse/2.0.0/update for a p2 repository that contains Hibernate.)
  • CDO Model Repository Server MongoDB (Contains the MongoDBStore plugins. Ensure that a MongoDB Java driver is already installed! Visit http://net4j.sourceforge.net/update for a p2 repository that contains a MongoDB Java driver.)
  • CDO Model Repository Server Objectivity (Contains the Objectivity Store and stubbed jar file bundle. For runtime, ensure that you have Objectivity /DB installed!)
  • CDO Model Repository Server Product (Contains the product definition of an installable CDO server.)
  • CDO Model Repository Server (Contains the CDO server plugins.)
  • CDO Model Repository Tests Hibernate (Contains the CDO Hibernate test plugins and sources. Ensure that Hibernate is already installed! Visit http://www.elver.org/eclipse/2.0.0/update for a p2 repository that contains Hibernate.)
  • CDO Model Repository Tests (Contains the CDO test plugins, models and sources.)
  • CDO Release Engineering Documentation (Contains the documentation of the CDO release engineering infrastructure.)
  • CDO Release Engineering Dynamic Working Sets (Contains a set of CDO-specific working sets that are automatically populated with the appropriate workspace projects.)
  • CDO Release Engineering Launch Decorator (Contains a label decorator that highlights unshared launch configurations to ease their removal.)
  • CDO Release Engineering Manifest Opener (Contains context-sensitive openers for plugin manifests (F6) and project properties (Shift+F6).)
  • CDO Release Engineering Relative Paths (Contains a popup action that copies the relative path between two workspace resources into the clipboard.)
  • CDO Release Engineering Tasks (Contains a decorator that appends the name of the assignee to a task label.)
  • CDO Release Engineering Version Tool (Contains an incremental builder that validates the micro versions of plugins against an implementation baseline using source digests.)
  • CDO Release Engineering Window Title Setter (Contains a plugin that sets the IDE window title to the name of the workspace location directory.)
  • CDO Release Engineering Windows Explorer (Contains a popup action that starts the Windows Explorer on the selected workspace resource.)
  • CDO Release Engineering Windows Git (Contains a popup action that starts a Git bash on the selected Git repository.)
  • Net4j DB Framework DB2 Adapter (Net4j DB Framework DB2 Adapter contains the DB2 Adapter matching the Net4j DB Framework BUT NOT the database driver bundle for DB2. This needs to be installed separately, for example from http://net4j.sourceforge.net/update)
  • Net4j DB Framework Derby Adapter (Contains the Derby Adapter matching the Net4j DB Framework and the database driver bundle for Derby.)
  • Net4j DB Framework Documentation (Contains the documentation of the Net4j DB Framework.)
  • Net4j DB Framework H2 Adapter (Contains the H2 Adapter matching the Net4j DB Framework and the database driver bundle for H2.)
  • Net4j DB Framework HSQLDB Adapter (Contains the HSQLDB Adapter matching the Net4j DB Framework BUT NOT the database driver bundle for HSQLDB. This needs to be installed separately, for example from http://net4j.sourceforge.net/update)
  • Net4j DB Framework MYSQL Adapter (Contains the MYSQL Adapter matching the Net4j DB Framework BUT NOT the database driver bundle for MYSQL. This needs to be installed separately, for example from http://net4j.sourceforge.net/update)
  • Net4j DB Framework PostgreSQL Adapter (Contains the PostgreSQL Adapter matching the Net4j DB Framework BUT NOT the database driver bundle for PostgreSQL. This needs to be installed separately, for example from http://net4j.sourceforge.net/update)
  • Net4j DB Framework (Contains the database core framework and database adapter plugins for Derby, Mysql, HSQLDB and PostgreSQL. Additional database drivers are available via http://net4j.sourceforge.net/update (read the license informations).)
  • Net4j Signalling Platform Definitions (Contains the EMF-based definition and wiring plugins for Net4j.)
  • Net4j Signalling Platform Documentation (Contains the documentation of the Net4j Signalling Platform.)
  • Net4j Signalling Platform Examples (Contains the general Net4j examples, the buddies collaboration + chat examples and the experimental JMS provider implementation plugins, as well as all sources.)
  • Net4j Signalling Platform Runtime (Contains the Net4j core and transport provider plugins (tcp, jvm and http).)
  • Net4j Signalling Platform SDK (Includes Runtime, UI, DB, Examples, Documentation and Source.)
  • Net4j Signalling Platform Tests (Contains the Net4j test plugins and sources.)
  • Net4j Signalling Platform UI (Contains the Net4j user interface and utilities user interface plugins.)
  • Net4j Utilities Documentation (Contains the documentation of the Net4j Utilities.)
  • Net4j Utilities UI (Contains the Net4j utilities user interface plugins.)
  • Net4j Utilities (Contains the Net4j utilities plugin.)

Table of Contents

Release Milestones

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 1 week; that is, until the final 3.8 release of the Platform, upon which CDO and other projects will release simultaneously. CDO will deliver its milestones within one week of the Eclipse Platform. It is anticipated that CDO will synchronize its milestones with the Juno milestone schedule.
M108/16/2011
M209/27/2011
M311/08/2011
M412/13/2011
M501/31/2012
M603/20/2012
API freeze
M705/08/2012
Feature Freeze
RC105/22/2012
RC205/29/2012
RC306/05/2012
RC406/12/2012
Final06/27/2012
CDO will produce maintenance releases to align with the Indigo SR releases, that includes the Eclipse Platform 3.7.x release. CDO may produce interim maintenance releases in addition to these in order to satisfy client requests. Maintenance releases will only be published if they have any new fixes to offer.
  • 09/24/2010 - CDO 4.0-SR1 maintenance release (Indigo Service Release 1)
  • 02/25/2011 - CDO 4.0-SR2 maintenance release (Indigo Service Release 2)
  • A list of issues indicated for the 4.0.x maintenance stream can be found in bugzilla, or by using links on maintenance stream build pages.

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The CDO Model Repository Project (CDO) depends upon on the Platform and other projects, which are mostly "pure" JavaTM. CDO will target the same Java version as EMF Core, which currently requires Java 5. Eclipse Platform SDK 3.8 will be tested and validated on a number of reference platforms. CDO will be tested and validated against a subset of those listed for the platform.

Internationalization

The CDO Model Repository is a runtime technology with most of the components having no user interface. The remaining user interface parts of CDO are considered exemplary and thus no attention has been paid to externalize them for internationalization.

Table of Contents

Compatibility with Previous Releases

The 4.1 release of the CDO Model Repository will contain a large set of new functionality and an enhanced API as driven by the community. Therefore CDO will not be binary compatible with previous releases, but API compatible.

Table of Contents

Themes and Priorities

A list of project requirements and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to indicate what major set of functionalities is to be concentrated on for each. These themes are presented below, while the requirements document and associated Bugzilla entries are left to those wanting more detailed information on each.

Power to the People

Major improvements in the API and configuration will give clients considerably more control over the behaviour and performance of their repositories and sessions.

Appealing to a Broader Community

The CDO project has a proven record of robustness and flexibility. However, in the past best results could only be achieved with EMF models specifically generated for the usage with CDO. The upcoming 3.0 release will be less invasive to the client models and applications by being better aligned with EMF and other standards.

Lighter, Faster and Better

The CDO project has a proven track record of quality, reliability, and extensibility but all these aspects can be continuously improved. Existing and new clients often desire more functionality from the framework while long established clients generally desire mostly improvements in performance. Often these two are at odds since additional extensibility often has a performance cost and any changes, even performance boosting ones, potentially impact reliability. Every effort will be made to introduce new capabilities so that they have negligible impact on established clients based on the guiding principle: if you don't use it, you don't pay for it. Because service and support has and always will take priority over new development work, development commitments and schedules are subject to arbitrary change, slippage, or even deferral. Be sure to establish direct communication to ensure that any hard commitments are seen as that by the development team itself!

Eclipse 4.2

No specific support, no testing on 4.2

Table of Contents

Appendix A: Legal Notices

  • Java is a trademark or a registered trademark of Sun Microsystems, Inc.
  • All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.

Table of Contents