Hi,
I'm seeing a few issues with the different versions of the same third party
jars pulled in.
1) Tuscany module A depends on geronimo-jta_1.1_spec-1.1.1.jar (which is an
OSGi bundle). The maven bundle plugin generate an Import-Package like
javax.transaction;version="1.1".
2) thirdparty-library pulls in geronimo-jta_1.1_spec-1.1.1.jar and
geronimo-jta_1.0.1B_spec-1.1.jar. It produces an Export-Package like:
javax.transaction;version="1.1", javax.transaction;version="1.0" (I'm
not sure if it's valid to have one bundle exports two different versions of
the same package)
This causes OSGi dependency resolution errors.
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
Sent: Monday, October 13, 2008 9:33 AM
To: <[email protected]>
Subject: Fixed generation of thirdparty-library bundle classpath
I've fixed the generation of the thirdparty-library bundle .classpath, so
the PDE should not hang anymore when you load it into your Eclipse
workspace.
Here's the current scheme, which seems to work well:
- Third party JARs are placed under thirdparty-library/lib by the Tuscany
Maven bundle plugin.
- That bundle's Manifest is generated by the plugin as well.
- The .classpath points to these JARs under lib instead of the JARs in the
Maven repos.
- Loading that project in your workspace will allow the PDE to resolve all
bundle imports of these third party packages.
Another option would be to generate an Eclipse update site with one bundle
per third-party JAR and ask the developer to add that update site to his
PDE's 'target platform', but that seems more complicated, and will make it
more difficult to see what the third-party JARs are as they won't show in
your Eclipse workspace.
Hope this helps.
--
Jean-Sebastien
