Bugzilla – Full Text Bug Listing
| Summary: | XSD Info Set (still) requires JDT, via update site | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> |
| Component: | Cross-Project | Assignee: | Cross-Project issues <cross-project.inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | David.Olsen, Ed.Merks, marcelop, mober.at+eclipse |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 106804 | ||
| Bug Blocks: | |||
|
Description
David Williams
Did you install the XSD SDK feature? Or just the individual XSD feature(s) you need? In the update manager on Europa site, I just selected xsd end user plugin (which I think was "smallest" one available. (In reply to comment #2) > In the update manager on Europa site, I just selected xsd end user plugin > (which I think was "smallest" one available. > Opps, I mean 'feature', of course. The request for being able to get EMF subfeatures which do not need JDT from the Europa site has been asked already in bug #106804 comment 44. Two options were proposed for satisfying this request. Thinking about his more, what would you think about this proposal: * All the small EMF component features need to be on the Europa site anyways, they are just not listed in the site.xml * Let's list them all in the Europa site.xml, but in a special category e.g. "Automatically included subfeatures" with a description "This category contains components which update manager selects automatically when "Select Required" is chosen. These are not meant for manual selection." Then, the WTP folk can just add EMF plugin dependencies into their feature.xml, on Europa choose WTP then "Select required" and they should get the right EMF featureset of small components they need but without codegen and without JDT... (and it would also make us DSDP folk happy for our TM Discovery component). Do you like apples? ;-) I spoke with Marcelo & Ed about this, and it's been suggested that rather than a) dropping 23 more emf/sdo/xsd features into Europa, or b) creating yet more features (or features-of-features) for 'with JDT' and 'without JDT', (Tastes Great! Less Filling! Desert Topping! Floor Wax! Spoon! Fork!) we could... c) simply drop two more features to Europa, emf.common and emf.ecore. Since these are really only useful as 'Enabling Features', I propose putting them in that category, so 'Select Required' can find them but J. Random Europa-User won't be burdened with them. How do you like those apples? Would that be enough to satisfy the need for an 'EMF Lite: all the flavour, none of the JDT' Europa feature? (Forgive the preceding perceived flippancy or sarcasm -- I'm just in a good mood today, despite the fact that features still... ahem... suck.) ;-) David (and cc: to John):
On further reflection, if I:
a) start with Eclipse 3.3RC1 SDK
b) use the RC1 Europa update site
c) pick WebTools' WST then hit Select Required...
... UM picks BOTH the org.eclipse.xsd feature and its SDK, too, which it should only be doing if you depend on something other than the org.eclipse.xsd plugin/feature.
If you depend on org.eclipse.xsd.ecore.{importer,exporter}, then you depend on JDT, and no amount of feature reorging will change that.
XSD SDK feature (contains...)
c> xsd.ecore.converter feature (contains...)
c> xsd.ecore.{importer,exporter} plugins (depends on...)
!> org.eclipse.emf.converter feature (contains...)
c> org.eclipse.emf.{importer,exporter} plugins (depends on...)
!> org.eclipse.jdt runtime feature (contains...)
c> org.eclipse.jdt.core plugin
Another test: a) start with Eclipse 3.3RC2 Platform Runtime Binary b) use the RC1 Europa update site AND the EMF Update site (http://download.eclipse.org/modeling/emf/updates/site-interim.xml) c) pick WebTools' WST then hit Select Required... The following 10 features get selected for install: wst gef emf.common + common.ui emf.ecore + emf.ecore.edit emf.edit + emf.edit.ui xsd + xsd.edit (.edit is what causes the XSD SDK feature to be selected) So, if you want to avoid installing the full EMF or XSD runtimes/SDKs (and thus requiring JDT), we'd need to provide 7 new "Enabling Features" to Europa. Would those 7 make DSDP TM Discovery happy too? (In reply to comment #7) > emf.common + common.ui > emf.ecore + emf.ecore.edit > emf.edit + emf.edit.ui These six features are exactly what TM Discovery needs, so yes this change would make us happy too :-) As I've heard no objections or 'please add feature X, too' I'll add these 7 new "Enabling Features" to Europa today. Martin, David: The last RC2 respin worked[1], so you now have 7 new features to play with. Can you run some tests using the staging site[2], and close this bug if you're both satisfied? Thanks! [1] http://dash.eclipse.org/~bfreeman/europa/#emf-emf [2] http://download.eclipse.org/releases/europa/staging/ (In reply to comment #10) > Can you run some tests using the staging site[2], and close this bug if you're > both satisfied? > I'm happy. I tested the RC2 staging area and I could install WST without JDT. Very nice! Thank you so much for your attention to this, and willingness to "work around" the fact that features still... ahem... :) Works perfectly fine for me as well, getting exactly the 6 small features I need. Awsome! Fixed in Europa 3.3RC2. |