Project Plan For MDT UML2, version 5.0.0

Introduction

This document lays out the feature and API set for the next release of the Eclipse Unified Modeling Language 2.x (UML2) Project, version 5.0.0. 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:
  • UML2 source code release, available as versions tagged "R5_0" in the project's git repository.
  • UML2 SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
  • UML2 runtime binary distribution (downloadable and update site).
  • UML2 stand-alone binary distribution (downloadable).
  • UML2 tests

Table of Contents

Release Milestones

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 1 day; that is, until the final 4.4 release of the Platform, upon which UML2 and other projects will release simultaneously. As UML2 is a dependency of numerous other projects, UML2 will deliver its milestones within one day of the Eclipse Platform. It is anticipated that UML2 will synchronize its milestones with the Luna milestone schedule.
M108/19/2013
M209/30/2013
M311/11/2013
M412/16/2013
M501/27/2014
M603/10/2014
API Freeze
M705/05/2014
Feature Freeze
RC105/19/2014
RC205/26/2014
RC306/02/2014
RC406/09/2014
Luna06/24/2014
UML2 will produce maintenance releases to align with the Kepler SR releases, that includes the Eclipse Platform 4.3.1 and 4.3.2 releases. UML2 may produce interim maintenance releases in addition to these in order to satisfy clients requests.
  • Friday, September 27, 2013 - UML2 4.1.1 maintenance release (Kepler Service Release 1)
  • Friday, February 28, 2014 - UML2 4.1.2 maintenance release (Kepler Service Release 2)
  • A list of issues indicated for the 4.1.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 Eclipse Unified Modeling Language 2.x (UML2) project depends upon on the Platform and other projects, which are mostly "pure" Java. The 4.4 release of the Eclipse Platform Project is written and compiled against versions 1.5 and 1.6 of the Java Platform APIs, and targeted to run on version 1.5 of the Java Runtime Environment, Standard Edition. UML2 will target the same Java version as EMF, which currently also requires Java 5. Eclipse Platform SDK 4.4 will be tested and validated on a number of reference platforms. UML2 will be tested and validated against a subset of those listed for the platform.

Internationalization

The Eclipse Platform is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. As a result, the UML2 project will provide English strings in its default bundles and be localized to a subset of those locales offered by the Platform. This plan will be updated to indicate which locales will be provided and the time frame for availability.

Table of Contents

Compatibility with Previous Releases

Compatibility of Release 5.0: The UML2 project will be developed in parallel, and released simultaneously, with the following projects. As stated above, each milestone release of the UML2 project will be compatible with the corresponding milestones for each of these projects, and delivered the appropriate offset.
  • Eclipse Platform SDK version 4.4
  • Eclipse Modeling Framework (EMF) version 2.10
Therefore, the UML2 initial release will be compatible with these versions and will publish binary and source compatibilities with migration guides on subsequent releases.

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.

Community Support

The UML2 project has a proven track record of quality and reliability. Service and support will take priority over new development work; commitments and schedules are subject to arbitrary change, slippage, or even deferral.
  • Committed

    • Investigate the proper usage of message bundles. [270181] (target milestone: M3)
    • Custom EMFv TraversalStrategy needed for stereotype applications [397508] (target milestone: M3)
    • Package merge should copy references on receiving package [176998] (target milestone: M3)
    • template expansion support [180744] (target milestone: M4)
    • UML2 runtime feature has many dependencies and includes too many unnecessary plugins for clients wanting only to use UML API to create/manipulate UML models [227616] (target milestone: M5)
    • no way to tell standard from convenience API [251963] (target milestone: M3)
    • Update ApplyStereotypeAction to select a resource location [268444] (target milestone: M3)
    • Create common superinterface for DataType, Interface and Class with operations-related methods [269598] (target milestone: M3)
    • Ant Task for Profile Definition [286404] (target milestone: M5)
    • Stereotype Profil [300957] (target milestone: M3)
    • Unapply stereotype is very counter-intuitve [326915] (target milestone: M3)
    • Make Getting Started Documentation more helpful [382342] (target milestone: M5)
    • Provide a routine to initialize the pathmap URI-mappings [401682] (target milestone: M3)
    • Initialize ePackageNsURIToProfileLocationMap for standalone usage [401804] (target milestone: M5)
    • Undesirable export of org.eclipse.emf.validation dependency [402206] (target milestone: M5)
    • [uml2ecore] Support for OCL non-api invariants [403374] (target milestone: M4)
    • Embedded OCL should track CamelCase UML to Ecore conversion [405061] (target milestone: M3)
    • OCL Property initializers should be copied during conversion to Ecore [405065] (target milestone: M5)
    • [Profile Definition] Invalid transformation from Profile to Ecore [409396] (target milestone: M3)
    • Editor creates LiteralString for Enumeration Property default [412912] (target milestone: M4)
    • EcorePrimitiveTypes has no URI [412917] (target milestone: M3)
    • Split out the individual subroutines of UMLResourcesUtil#init(ResourceSet) [414572] (target milestone: M3)
    • UML2Ecore should add oppositeRoleName annotations [420338] (target milestone: M5)

Compliance

As an implementation of the OMG's UML specification, the UML2 project will maintain currency with the revised 2.5 specification.
  • Committed

    • DurationObservation#event should be ordered [384336] (target milestone: M6)
    • Support for UML 2.5 [418466] (target milestone: M6)
    • UML2Ecore should strip result = from bodyConstraints [419324] (target milestone: M6)
    • UML 2.5 model fails to generate [420330] (target milestone: M6)

Table of Contents

Appendix Legal Notices

  • Java is a trademark or a registered trademark of Sun Microsystems, Inc.
  • UML and OMG are trademarks or registered trademark of the Object Management GroupTM, 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

view raw xml of project plan
from project meta-data key "projectplanurl"