Bugzilla – Full Text Bug Listing
| Summary: | Inconsistent EMF/XSD SDK description | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Ed Willink <ed> |
| Component: | Core | Assignee: | Kenn Hussey <Kenn.Hussey> |
| Status: | CLOSED FIXED | QA Contact: | Kenn Hussey <Kenn.Hussey> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | Kenn.Hussey |
| Version: | 2.7.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Ed Willink
Kenn, I'm really not sure what Ed is driving at, are you? I'm not sure why others would ever put dependencies on an SDK feature; there are certainly a plethora of finer grained features already... I'd like to avoid having even more composite features when clients can simply depend on multiple finer grained features. Well, EMF has evolved over the past year or so to include a number of SDKs and target components for different purposes. - "EMF SDK", the original SDK with dependencies only on the platform. - EMF runtime target components for RAP (also with an associated "SDK", which includes source). - EMF runtime target components for GWT (also with an associated "SDK", which includes source). - "EMF ODA SDK", a new SDK with an additional dependency on DTP. The "All-In-One" SDK was introduced as a convenience (some years ago), and has always been intended as the sum total of everything from the EMF (Core) and (MDT) XSD projects which can be installed into an IDE. This is still the case, except it now includes more than it did in the past and will continue to include new things if/when we introduce them. Rather than creating yet another new feature, to slice/dice the projects in different ways, I would suggest installing (or creating dependencies on) exactly what you need. I typically avoid installing the All-In-One SDK, because it includes examples which have an undesirable effect on code generation (i.e., it generates additional sample artifacts). Instead, I usually install "EMF SDK" and "XSD SDK"; if you want/need the examples as well, then install those too. When working with M* builds the contents of repositories are so uncertain and slow that I always download all the M* Update Zips, and do local installs one at a time with contact all sites switched off. Once downloaded, this is particualrly useful since it is often necessary to recreate a number of tines to try to pin down suspected JDT, EMF, ... bugs. In the past EMF and GEF All-In-One SDKs were the first to install, since they provided everything that was nedded downstream. The EMF All in One SDK became useless during Heklios dev becuase it crashed the install with undesirable RAP contributions, so it became necessary to be very selective for a bit. The EMF SDK was useful in M4 as a way to avoid ODA dependencies. Now in M5 the EMF and XSD SDKs have been split so that there is no feature that corresponds to the traditional everything that is good and nothing that is bad for a standard installation. From the descriptions the EMF+XSD SDK is what is needed but the description is at variance with content since there is an undescribed ODA dependency. (In reply to comment #3) > The EMF SDK was useful in M4 as a way to avoid ODA dependencies. The EMF SDK in M5 doesn't depend on ODA either... > Now in M5 the EMF and XSD SDKs have been split so that there is no feature that > corresponds to the traditional everything that is good and nothing that is bad > for a standard installation. The EMF and XSD SDKs have always been separate... so no change here for M5 either. In fact, there have been no changes from M4 to M5 in terms of how the features are structured... > From the descriptions the EMF+XSD SDK is what is needed but the description is > at variance with content since there is an undescribed ODA dependency. I can look into tweaking the description to make it more generic, if that helps... Any suggestions? It was version 1.13 of org.eclipse.emf.all-feature/feature.xml that changed the "The combined SDK for EMF and XSD, including source, documentation, and examples" feature from EMF SDK EMF Examples XSD SDK XSD Examples to EMF SDK EMF Examples XSD SDK XSD Examples ODA SDK which is the change I'm complaining about. This feature is 'broken' for me; it is no longer installable on a naked platform. If the change really is necessary then the description should at least change to "The combined SDK for EMF, XSD and ODA, including source, documentation, and examples, requiring ... to support ODA." The changes have been committed to CVS. The fix is available in 3.7RC3 and later. |