Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] Target platform manifest problem.

Title: Re: [pde-dev] Target platform manifest problem.
In this case, the bundle in question was the com.springsource.org.joda.time v1.6.0 bundle from the SpringSource Bundle Repository.

The only problem with the bundle is that the Bundle-SymbolicName header was spelled Bundle-Symbolicname.

I used the most excellent bnd tool from Peter Kriens at http://www.aqute.biz/Code/Bnd  to simply repackage the bundle with the more common manifest header in place, no other changes. Most jars can be packaged easily with this tool. Others require some thought on what should be imported/exported. But in all cases, the tool makes it simple.

When you combine the bnd tool with maven via the maven-bundle-plugin, then you can automate the downloading of the jar to be wrapped, and wrap it and deploy it to a maven repo all in one step. I usually just set up a simple project with a pom file only for its contents, and do it that way. I can provide an example for that particular jar if you like.

--
Best Regards,

Don Laidlaw | Sr. Research Engineer |
Infor | office: +1 902-576-5185 | mobile: +1 902-401-6771 | don.laidlaw@xxxxxxxxx




From: Chris Aniszczyk <zx@xxxxxxxxxxxxxxxxx>
Reply-To: "Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>
Date: Tue, 8 Sep 2009 14:49:03 -0400
To: "Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>
Subject: Re: [pde-dev] Target platform manifest problem.

On a side note, how are you creating your third party bundles?

Cheers,

--
Chris Aniszczyk | EclipseSource Austin | +1 860 839 2465
http://twitter.com/eclipsesource | http://twitter.com/caniszczyk


Back to the top