| Summary: | Will GMF Tooling produce a 2.3.2 to match GMF Runtime 1.4.2? | ||
|---|---|---|---|
| Product: | [Modeling] GMF-Tooling | Reporter: | Kit Lo <kitlo> |
| Component: | Core | Assignee: | Project Inbox <gmp.gmf-tooling-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse |
| Version: | 2.3.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Kit Lo
This issue will only occur for users taking advantage of the ZIP downloads.
For example, for Helios SR1 , gmf-sdk-2.3.1.zip includes the contents of gmf-sdk-runtime-1.4.1.zip (and gmf-sdk-runtime-1.4.1.zip includes gmf-sdk-notation-1.4.1.zip).
For Helios SR2, there will be new releases of GMF Runtime and GMF Notation, so gmf-sdk-runtime-1.4.2.zip will include gmf-sdk-notation-1.4.2.zip.
There will not be a GMF Tooling release for SR2, so no gmf-sdk-2.3.2.zip.
GMF Tooling does not have a built in dependency to GMF Runtime, just like its dependency on EMF, so there is no technical need to build a GMF Tooling SR2 when there are no content changes.
i.e. the feature.xml contains:
<requires>
<import feature="org.eclipse.emf" version="2.6.0" match="compatible"/>
<import feature="org.eclipse.gef" version="3.6.0" match="compatible"/>
<import feature="org.eclipse.ocl" version="3.0.0" match="compatible"/>
<import feature="org.eclipse.emf.validation" version="1.4.0" match="compatible"/>
<import feature="org.eclipse.gmf.runtime.sdk" version="1.4.0" match="compatible"/>
</requires>
For Helios SR2, clients who are not using update sites but are using ZIP files as their download, will need to manually update their ZIP. (i.e. unzip SR1 and update with SR2 files).
|