| Dependency version mismatch when materializing a plugin [message #981884] |
Mon, 12 November 2012 19:33  |
 Andrea Richiardi
Messages: 64
Registered: August 2012 |
Member |
|
|
Hello dear Bucky friends!
Ok, now I have a working materialization of my plugin, that takes its dependency from a target platform, materialized somewhere else.
The new plugin correctly have the last SVN revision instead of the .qualifier string and carries a MANIFEST.MF.
The problem is that the org.eclipse.core.runtime specified in the Require-Bundle section, in this newly built jar, doesn't match the version I have in my target platform.
I thought Bucky was actually matching the required version (reading it in the MANIFEST.MF contained in the SVN repository) and then reporting the same version in the new materialized plugin package.
But I have this in the log:
org.eclipse.core.runtime:osgi.bundle: Found match 3.5.0.v20090525
And this in the new MANIFEST.MF:
Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.8.0,4.0.0)"
When I try to import the plugin, it doesn't work (of course) because the version cannot be found the 3.8 version...
What am I doing wrong? 
Thank you guys!
[Updated on: Mon, 12 November 2012 19:33] Report message to a moderator |
|
|
| Re: Dependency version mismatch when materializing a plugin [message #982784 is a reply to message #981884] |
Tue, 13 November 2012 12:14  |
|
Hi 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?
Quote:I thought Bucky was actually matching the required version (reading it in the MANIFEST.MF contained in the SVN repository)
How does it looks like? Could you post the original MANIFEST.MF from the SVN?
Best regards,
Dennis.
+Dennis Huebner
Get professional support from the Xtext committers at www.typefox.io
|
|
|
| Re: Dependency version mismatch when materializing a plugin [message #982970 is a reply to message #982784] |
Tue, 13 November 2012 15:21 |
Andrea Richiardi
Messages: 64
Registered: August 2012 |
Member |
|
|
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 16:21] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04460 seconds
] 
Search
Help
Register
Login
Home
