The project leadership certifies that the APIs in this release are "Eclipse Quality".
The Amalgamation 1.4 release will bring :
- an integrated ready-to use bundle through the Kepler Modeling Package
- complementary UIs to discover and install other modeling components.
The discovery UI is leveraging a model describing its contribution and hosted on the Eclipse.org server. This model might be updated after the release to provide new installable components for the package.
The Modeling Package is tested manually with each milestone.
Metamodel definitions and interfaces of the modeling discovery are considered APIs.
Non-API classes are separated from the exposed API through an "internal" namespace.
Non-API packages are exported with an internal visibility as such they are visible but with an illegal access warning.
Documentation is kept on the Eclipse Wiki http://wiki.eclipse.org/ModelingAmalgam . Work has been done during the Google Summer of Code 2011 to document the modeling projects, the result has not been integrated in Eclipse itself but is available through github : http://model-driven-blogging.blogspot.fr/2011/09/eclipse-modeling-definitive-tutorial.html
Amalgam address the need of a common integrated platform for Eclipse Modeling. This platform is completely focused on the EMF runtime and technologies. The discovery UI integrated in the package address the need to find its way through the so diverse modeling project and to install the needed technologies.
The Amalgam integration code is conforming to the user interface guidelines.
The Modeling Examples developed for the Eclipse Modeling Project: A Domain-Specific Language (DSL) Toolkit (ISBN-13: 978-0321534071) book have not been maintained since the Ganymede release and have not been updated for Kepler yet. Any help is welcome.
No standard exists concerning the modeling amalgam project scope.