Eclipse Community Forums: Rich Client Platform (RCP) » "Some inter-plug-in dependencies have not been satisfied" error when the missing plug-ins

Home » Eclipse Projects » Rich Client Platform (RCP) » "Some inter-plug-in dependencies have not been satisfied" error when the missing plug-ins (build error)

Show: Today's Messages :: Show Polls :: Message Navigator

"Some inter-plug-in dependencies have not been satisfied" error when the missing plug-ins [message #548284]

Wed, 21 July 2010 11:18

Ian Leslie

Messages: 137
Registered: July 2009

Senior Member

After upgrading to Eclipse 3.6 (from 3.4.2) I updated my rcp target platform and my app runs fine in debug mode from the IDE on Windows. Then I performed my full build, for the other platforms, and added a few missing plug-ins to the target platform but I am still left with errors:

[eclipse.generateFeature] Some inter-plug-in dependencies have not been satisfied.
[eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

I am not sure what is missing. I have all four of those plug-ins in the target platform and they depend on org.eclipse.equinox.launcher which is also present. I'm not sure what else to look at.

Any advice or help would be appreciated.

Thanks,

Ian

build command line:

"C:\Program Files\Java\jdk1.6.0_13/bin/java.exe" -jar "c:\Program Files\Eclipse36\eclipse/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar" -application org.eclipse.ant.core.antRunner -buildfile "c:\Program Files\Eclipse36\eclipse/plugins/org.eclipse.pde.build_3.6.0.v20100603/scripts/productBuild/productBuild.xml" -Dbuilder="p:\WizardsFamiliar2/wizardsfamiliar.builder"

full build output:

Buildfile: c:\Program Files\Eclipse36\eclipse/plugins/org.eclipse.pde.build_3.6.0.v20100603/scripts/productBuild/product
Build.xml

main:

preBuild:

preSetup:

checkLocalMaps:

getMapFiles:

postSetup:

checkLocalBase:

getBaseComponents:

processRepos:

generateFeature:

fetch:

generateFeature:
[eclipse.generateFeature] Some inter-plug-in dependencies have not been satisfied.
[eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.generateFeature] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

generate:

preGenerate:

allElements:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

init:

generateScript:
[eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied.
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.gtk.linux.x86_64:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86:
[eclipse.buildScript] Bundle org.eclipse.equinox.launcher.win32.win32.x86_64:

BUILD FAILED
c:\Program Files\Eclipse36\eclipse\plugins\org.eclipse.pde.build_3.6.0.v20100603\scripts\productBuild\productBuild.xml:4
2: The following error occurred while executing this line:
C:\Program Files\Eclipse36\eclipse\plugins\org.eclipse.pde.build_3.6.0.v20100603\scripts\build.xml:91: The following err
or occurred while executing this line:
p:\WizardsFamiliar2\wizardsfamiliar.builder\customTargets.xml:58: The following error occurred while executing this line
:
C:\Program Files\Eclipse36\eclipse\plugins\org.eclipse.pde.build_3.6.0.v20100603\scripts\genericTargets.xml:107: Unable
to find feature: org.eclipse.rcp.

Total time: 12 seconds

Report message to a moderator

Re: "Some inter-plug-in dependencies have not been satisfied" error when the missing plug- [message #549606 is a reply to message #548284]

Tue, 27 July 2010 11:05

Ian Leslie

Messages: 137
Registered: July 2009

Senior Member

I'm still mystified but I have learned a few more things.

I have manually verified that all plug-ins referenced by org.eclipse.rcp are there in the target platform.

The four plug-ins that generate error messages are there and their dependencies are also all there in the target platform.

BTW the four plug-ins that generate the error messages are the four platforms I am trying to have built. they appear in my customTargets.xml file thusly:

	<!-- ===================================================================== -->
	<!-- Targets to assemble the built elements for particular configurations  -->
	<!-- These generally call the generated assemble scripts (named in -->
	<!-- ${assembleScriptName}) but may also add pre and post processing -->
	<!-- Add one target for each root element and each configuration -->
	<!-- ===================================================================== -->

	<target name="assemble.wizardsfamiliar.product.feature.win32.win32.x86">
		<ant antfile="${assembleScriptName}" dir="${buildDirectory}">
			<property name="archiveName" value="WizardsFamiliar-2.0-${buildType}${buildId}-win32.zip" />
		</ant>
	</target>

	<target name="assemble.wizardsfamiliar.product.feature.win32.win32.x86_64">
		<ant antfile="${assembleScriptName}" dir="${buildDirectory}">
			<property name="archiveName" value="WizardsFamiliar-2.0-${buildType}${buildId}-win64.zip" />
		</ant>
	</target>

	<target name="assemble.wizardsfamiliar.product.feature.linux.gtk.x86">
		<ant antfile="${assembleScriptName}" dir="${buildDirectory}">
			<property name="archiveName" value="WizardsFamiliar-2.0-${buildType}${buildId}-linux-gtk32.zip" />
		</ant>
	</target>

	<target name="assemble.wizardsfamiliar.product.feature.linux.gtk.x86_64">
		<ant antfile="${assembleScriptName}" dir="${buildDirectory}">
			<property name="archiveName" value="WizardsFamiliar-2.0-${buildType}${buildId}-linux-gtk64.zip" />
		</ant>
	</target>

Is there anything else I should check? Any other avenues of investigation that someone could suggest would be appreciated.

There is one other thing that concerns me. When I created my target platform I followed the same packing list I used for my 3.4 based build. However there was one .zip package that was significantly different: RCP SDK

In 3.5 and 3.4 before that http:// download.eclipse.org/eclipse/downloads/drops/R-3.5.2-2010021 11343/index.php the RCP SDK had multiple entries and the .zip file had names like "eclipse-RCP-SDK-3.5.2-win32.zip"

In 3.6 http:// download.eclipse.org/eclipse/downloads/drops/R-3.6-201006080 911/index.php the RCP SDK has only one entry and the .zip file is called "org.eclipse.rcp.source-3.6.zip"

I this really an expected change? It seems like all the platform SDK files have been bundled together into one package. Why the name change? Is this right?

Thanks,

Ian

Report message to a moderator

Re: "Some inter-plug-in dependencies have not been satisfied" error when the missing plug- [message #549632 is a reply to message #549606]

Tue, 27 July 2010 11:31

Daniel KrÃ¼gler

Messages: 853
Registered: July 2009

Senior Member

On 27.07.2010 13:05, Ian Leslie wrote:
> I'm still mystified but I have learned a few more things.
>
> I have manually verified that all plug-ins referenced by org.eclipse.rcp
> are there in the target platform.
>
> The four plug-ins that generate error messages are there and their
> dependencies are also all there in the target platform.

I can only confirm, that the error messages produced by the
Eclipse headless build are often hard to interpret - if at all!

You probably need to go through the list of *all* failures and check
each one. Quite often it is not the first hit. I haven't found any
systematic in these messages.

Good luck & Greetings from Bremen,

Daniel Krügler

Report message to a moderator

Re: "Some inter-plug-in dependencies have not been satisfied" error when the missing plug- [message #549677 is a reply to message #549632]

Tue, 27 July 2010 14:09

Ian Leslie

Messages: 137
Registered: July 2009

Senior Member

Daniel Krügler wrote on Tue, 27 July 2010 07:31

I can only confirm, that the error messages produced by the
Eclipse headless build are often hard to interpret - if at all!

You probably need to go through the list of *all* failures and check
each one. Quite often it is not the first hit. I haven't found any
systematic in these messages.

Sage advice. I too find the error messages less helpful than I would expect / desire. I was about to write to you that I had in fact checked everything - I thought I had. But before I did I checked again.

What through me most was the lack of missing any named plug-in under the first error about missing dependencies. I thought that was where the message about missing org.eclipse.rcp feature came from. But then I remembered something odd about the rcp feature in my target platform - it is a jar file and not a directory.

I tried this experiment - I unzipped the org.eclipse.rcp_3.6.0.v20100519-9OArFKvFtsd7WLUKh-DcYTS.jar file into a like named (minus .jar) folder and did the same for the source feature. Nine minutes later the build had finished successfully.

Now the only remaining questions are: Should the rcp feature be a .jar file? Did I get the wrong thing? Is this a bug in the distro or a problem with my build scripts that needs adjusting?

Thank you,

Ian

Report message to a moderator

Previous Topic:	RCP Application on AIX/Motif
Next Topic:	Exception while startup causes Debugging disabled???

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 07:06:21 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter