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.
MWE/HeliosReview
Contents
This page provides the required docuware for the MWE v1.0.0 Release Review', as part of the upcoming Helios Simultaneous Release.
Sven Efftinge (sven.efftinge@itemis.de)
Release Review : June 11, 2010
Communication Channel : eclipse.technology.emft newsgroup
Process Documentation : http://www.eclipse.org/projects/dev_process/development_process.php
Overview
The modeling workflow engine (MWE) allows to wire up complex compiler or transformation chains. It is based on Java and dependency injection and is therefore highly extendable. Based on a dependency injection framework, one can simply configure and wire up 'workflows' using a declarative domain-specific language. The project provides the runtime used to execute workflows as well as the IDE tooling used to edit, start and debug them.
Features
In this release MWE was completely overhauled. MWE2 is a concise textual DSL based on Xtext and provides deep integration with JDT. Also the runtime model has been slimmed down to the bare necessity to make it easier for users to leverage the framework and come up with own workflow components.
Non-Code Aspects
Documentation has been overhauled and extended.
Testing & Packaging
MWE makes use of the eclipse.org Hudson new continuous build system.
MWE is integrated into the Helios Release Train since Oktober 2009.
Community & Support
- Active newsgroup with several posts a week
- Presentation at EclipseCon
- Blog posts on planet.eclipse.org
- Bugs changed between 2009-07-01 and 2010-05-28:
IP Issues
The component leadership verifies that:
- the about files and use licenses are in place as per the Guidelines to Legal Documentation.
- all contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
- all significant contributions have been reviewed by the Foundation's legal staff.
- all non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff.
- all Contribution Questionnaires have been completed.
- the "provider" field of each plug-in is set to "Eclipse Modeling Project“.
- the "copyright" field of each feature is set to the copyright owner (the Eclipse Foundation is rarely the copyright owner).
- any third-party logos or trademarks included in the distribution (icons, help file logos, etc) have been licensed under the EPL.
- any fonts or similar third-party images included in the distribution (e.g. in PDF or EPS files) have been licensed under the EPL.
The MWE IP Log is available from [1]
Project Plan
The current project plan is available from [2].