|
|
Re: Dependency version mismatch when materializing a plugin [message #982970 is a reply to message #982784] |
Tue, 13 November 2012 10:21   |
Eclipse User |
|
|
|
Dennis Huebner wrote on Tue, 13 November 2012 07:14Hi Andrea,
I would say either you have a wrong target platform or you plugin's MANIFEST.MF has a wrong dependency.
Could you please post your TP definition?
My cquery contains:
<cq:advisorNode namePattern=".*" useTargetPlatform="false"/>
Does my TP contain what is materialized by Bucky? I am trying withing the Eclipse IDE (Juno) for now, I haven't tried with the headless build yet.
Quote:How does it looks like? Could you post the original MANIFEST.MF from the SVN?
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: com.myplugin.ui
Bundle-SymbolicName: com.myplugin.ui;singleton:=true
Bundle-Version: 3.3.0.qualifier
Bundle-Activator: com.myplugin.ui.Activator
Bundle-ClassPath: .,
lib/fop.jar,
lib/avalon-framework-4.2.0.jar,
lib/batik-all-1.7.jar,
lib/commons-io-1.3.1.jar,
lib/commons-logging-1.0.4.jar,
lib/serializer-2.7.0.jar,
lib/xalan-2.7.0.jar,
lib/xercesImpl-2.7.1.jar,
lib/xml-apis-1.3.04.jar,
lib/xml-apis-ext-1.3.04.jar,
lib/xmlgraphics-commons-1.4.jar
Require-Bundle: org.eclipse.core.runtime,
org.eclipse.ui,
org.eclipse.ui.views,
org.eclipse.core.expressions
Bundle-ActivationPolicy: lazy
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-Vendor: XXX
Import-Package: org.eclipse.swt.widgets
I know that the version is not specified here, but it is on purpose. What happens then after the resolution phase (that gets the correct version as you can see in my previous post) if there is no version specified in this Manifest?
[Updated on: Tue, 13 November 2012 11:21] by Moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.35395 seconds