Reputation: 4351
When running my eclipse e4 application it shows that problems have been detected when validating.
This can be fixed by going to run configurations and selecting Add Required Plug-ins
but this is more of a work around then a fix.
I've tried changing the versions and adding/removing plugins but can't figure out how to solve these errors.
A similar issue is mentioned here.
What could be causing this?
Upvotes: 5
Views: 8229
Reputation: 41
I run into the same issue with the same behaviour, that if "add missing dependencies automatically" these kind of missing dependencies where gone. Adding org.apache.felix.src to launch config/product fixes this.
However: I have already the org.eclipse.e4.feature added to my product. If org.apache.felix.src is of such importance - why is it not put into the feature as dependency of the feature? Or asked the other way round: How should one resolve this without knowing that org.apache.felix.src is missing? There is no hint or something else that points to the missing dependency. Just the Require-Capability missing messages. Is there a way to do "bughunting" that leads to the missing dependency I am not aware of?
Or would this rather be an issue to be asked within the eclipse forum to get an answer from the developers?
Upvotes: 0
Reputation: 4351
I managed to find the missing plugins by comparing my run configuration before and after clicking Add Required Plug-ins
.
There were 5 plugins missing that clicking Add Required Plug-ins
in the product file didn't add.
org.apache.felix.scr
org.eclipse.equinox.event
org.eclipse.compare.core
org.eclipse.fx.osgi
org.eclipse.team.core
After adding these plug-ins to the product file and manifest the missing constraints problem was resolved.
Upvotes: 6
Reputation: 1286
If you add org.eclipse.equinox.ds
to your Required Plug-ins in MANIFEST.MF
then this dialog will not show up at launch.
Upvotes: 9