Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
ModelingAmalgam
The Modeling Amalgamation Project (just amalgam for short) will provide improved packaging, integration, and usability of Modeling project components.
Packages
Amalgam will deliver packages designed to target the different user communities of Modeling technology. Initially, a package will be created to form the basis of a Modeling package for Ganymede, and will likely evolve into the package for "Toolsmiths" to use in developing model-centric applications using EMF, GMF, etc. Another package will provide what "Practitioners" will expect to have available for end user tooling, such as UML2 Diagramming. Additionally, some branded packages may become available from Amalgam, such as the set of modeling capabilities from the original openArchitectureWare component, which has subsequently been dispersed across a range of Modeling projects.
Eclipse IDE for Software Architects and Modeling
The first package offered by Amalgam defines the Modeling Package available from the Eclipse Packaging Project.
Currently, this package includes the following Modeling features (including their dependencies), although more are expected to be added.
Modeling
- org.eclipse.emf.*
- org.eclipse.emf.emfqtv.all.sdk
- org.eclipse.gmf.sdk
- org.eclipse.m2m.qvt.oml.sdk
- org.eclipse.ocl.all.sdk
- org.eclipse.uml2.sdk
- org.eclipse.uml2tools.sdk
- org.eclipse.xsd
Dependencies
- org.eclipse.cvs
- org.eclipse.draw2d
- org.eclipse.gef
- org.eclipse.equinox.p2.user.ui
- org.eclipse.help
- org.eclipse.jdt
- org.eclipse.pde
- org.eclipse.platform
- org.eclipse.rcp
Other
- org.eclipse.epp.usagedata.feature (an obligatory aspect of the packaging project)
Opting In
Similar to the Eclipse Ganymede release train itself, Modeling projects and components will need to "opt-in" and satisfy a set of Must Do and Recommended elements.
Before becoming part of an Amalgam package offering, projects/components must satisfy these items:
| Item | Rationale |
|---|---|
| Branding cleanliness | As packages may form the basis of commercial products, they will need to be as "clean" as possible (feature/plug-in names, providers, legal documents, icons, etc.). This is also just good Eclipse citizenship. |
| TBD, | TBD |
Additionally, it is recommended that projects/components satisfy the following items as well:
| Item | Rationale |
|---|---|
| TBD, | TBD |
Reviews
In order to assess what is required from Amalgam in its mission to improve packaging, integration, and usability, a series of package reviews will be performed. Reviews will lead to the creation of bugs to be assigned to either a Modeling project/component, or to the Amalgam project to improve integration and functionality offered by the package. Below are the list of package milestone reviews completed to date: