Community
Participate
Working Groups
Due to the fact that UM only works with features, not plugins, you get unresolvable errors when trying to install TPTP features if you don't have EMF installed, such as: TPTP Monitoring Project Examples (4.2.0.v200606121835--0842282835373A) requires plug-in "org.eclipse.emf.ecore". Instead of depending on the ecore plugin, you should depend on the emf feature. Assigning to Component "Build" as I don't see one for Examples.
Created attachment 54803 [details] UM error dialog showing config problems (depending on plugin, not feature) FYI, the only workaround for this config problem is to install EMF before trying to install TPTP features. If you try to install them at the same time, you should still get this error.
Moving to monitoring project at Nick's request
Nick, I think what you are observing is not a bug. The TPTP feature you selected requires an EMF feature/plugin. Since it is not installed, you get an error and UM won't install the TPTP feature until all dependencies are installed. You can click on the "Select Required" button to select the dependencies automatically. Feature xml lets you specify requirements in the form of both features and plugins. The update manager looks at the requirement section of features to determin dependencies.
Update Manager does not resolve plugin dependencies. It will only work if your features depend cross-project on other projects' FEATURES, not their plugins. I don't have a problem with TPTP's features depending on TPTP's plugins, only on EMF's plugins. It's easy to reproduce this effect - just take a clean Eclipse and try to install TPTP by adding both the EMF and TPTP UM sites. It won't work, since plugin dependencies on EMF cannot be resolved (as shown in the attached screen shot). If you don't consider this a bug (that is, an installation usability issue), then so be it, but this is the sort of problem that will reappear during Europa testing and cause problems for TPTP adoption for newbies who don't already use EMF.
Updated target to match the iteration when this defect was processed
Since depending on plugins now works in Eclipse 3.3M7+, I agree, this bug is invalid.