Description Adrian Price 2019-04-15 12:16:33 EDT

Noticed while attempting to Build org.eclipse.test_3.7.200.v20170511-1043, having imported it from the target platform into the workspace then added it to site.xml. The Build command fails with the following exception:

Processing inclusion from feature org.eclipse.test: Bundle org.mockito_1.9.5.v201605172210 failed to resolve.:
	Unsatisfied import package COM.jrockit.reflect_0.0.0.
	Unsatisfied import package jrockit.vm_0.0.0.
	Unsatisfied import package org.hamcrest_[1.0.0,2.0.0).
	Unsatisfied import package sun.reflect_0.0.0.

NOTE that in org.mockito_1.9.5.v201605172210/META-INF/MANIFEST.MF, Import-Package specifies resolution:=optional for COM.jrockit.reflect, jrockit.vm and sun.reflect, and that the non-optional import of org.hamcrest_[1.0.0,2.0.0) ought, I would have thought, to have been satisfied by the inclusion of a compatible version of that bundle in org.eclipse.test_3.7.200.v20170511-1043's feature.xml, thus:

   <plugin
         id="org.hamcrest.core"
         download-size="53"
         install-size="111"
         version="1.3.0.v201303031735"
         unpack="false"/>
...
   <plugin
         id="org.hamcrest.library"
         download-size="62"
         install-size="142"
         version="1.3.0.v201505072020"
         unpack="false"/>

I also tried importing those exact versions of the above into the workspace as binary plug-ins, to no avail.

So this leaves me with two questions:
1. Why do unresolved *optional* Import-Package statements in a downstream dependency cause the feature build to fail?
2. Why doesn't the feature build resolve a non-optional Import-Package statement in a downstream dependency to a compatible version of the containing plug-in when that plug-in is explicitly included in the manifest of the feature being built?