Sorry, working on implementing signing but that is not ready for prime time and the imports were not removed ... I have updated 0.0.110 with cleaned up sources.
Kind regards, Peter Kriens CS> BTW there are unneeded imports that make the compilation fail with the CS> sources inside that jar CS> bnd\src\main\java\aQute\bnd\main\bnd.java:[13,0] package CS> aQute.lib.signing does not exist CS> bnd\src\main\java\aQute\lib\osgi\Builder.java:[5,0] package CS> aQute.lib.signing does not exist CS> On 2/8/07, Peter Kriens <[EMAIL PROTECTED]> wrote: >> I deployed it to 109 :-( >> >> http://www.aqute.biz/repo/biz/aQute/bnd/0.0.110/bnd-0.0.110.jar >> >> I have a flag in the deploy to update the version in the bnd file but >> it is not the default, maybe should change this. >> >> Kind regards, >> >> Peter Kriens >> >> CS> On 2/8/07, Peter Kriens <[EMAIL PROTECTED]> wrote: >> >> See if I understand. You want to have a bundle classpath and a target >> >> jar T. Bnd should then assume the contents of T are all exports but use >> >> the versions from the classpath for imports? >> >> >> >> If so, it must be your lucky day! :-) >> >> CS> seems we implemented the same thing at the same time ;) >> >> >> >> >> I have changed the bnd wrap command to accept a classpath and >> >> calculate the Export-Package statement from the contents of the target >> >> jar. Read more: >> >> >> >> http://www.aqute.biz/Code/Bnd#wrap >> >> >> >> I have not exhaustively tested it but it was a small change ... and it >> >> seemed to work for the jars I tried. Latest version is 0.0.110. >> >> >> >> http://www.aqute.biz/Code/Download >> >> CS> it's not showing up, the link there is broken >> >> >> >> >> Kind regards, >> >> >> >> Peter Kriens >> >> >> >> >> >> >> >> >> >> CS> yes, i've seen that, and was my first implementation for the maven >> >> CS> plugin, but it misses the version information on the imports. >> >> CS> Would that be an acceptable feature for BND? >> >> >> >> CS> On 2/6/07, Peter Kriens <[EMAIL PROTECTED]> wrote: >> >> >> It is ok for bnd to not find the imports, you just do not get any >> >> >> versions. >> >> >> >> >> >> The bnd command line has a wrap command that seems to do what you >> >> >> want. http://www.aqute.biz/Code/Bnd >> >> >> >> >> >> Kind regards, >> >> >> >> >> >> Peter Kriens >> >> >> >> >> >> CS> This may be more a BND question, but here it goes >> >> >> >> >> >> CS> Is there a way to generate a bundle that matches exactly the >> >> >> contents >> >> >> CS> of a jar (besides the manifest of course)? >> >> >> >> >> >> CS> For what I've seen so far you need to pass the whole classpath to >> >> >> BND >> >> >> CS> so it can generate import headers with versions, and >> >> >> EXPORT_PACKAGE to >> >> >> CS> tell it what packages you want. i'm looking for an easy way to to >> >> >> CS> express export everything in this jar and nothing else. IIRC that >> >> >> was >> >> >> CS> the way the osgi maven plugin worked, creating bundles 1 to 1 from >> >> >> CS> jars. >> >> >> >> >> >> CS> tia >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Peter Kriens Tel +33467542167 >> >> >> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens >> >> >> 34160 Beaulieu, France ICQ 255570717 >> >> >> Skype pkriens Fax +1 8153772599 >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Peter Kriens Tel +33467542167 >> >> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens >> >> 34160 Beaulieu, France ICQ 255570717 >> >> Skype pkriens Fax +1 8153772599 >> >> >> >> >> >> >> >> >> -- >> Peter Kriens Tel +33467542167 >> 9C, Avenue St. Drézéry AOL,Yahoo: pkriens >> 34160 Beaulieu, France ICQ 255570717 >> Skype pkriens Fax +1 8153772599 >> >> -- Peter Kriens Tel +33467542167 9C, Avenue St. Drézéry AOL,Yahoo: pkriens 34160 Beaulieu, France ICQ 255570717 Skype pkriens Fax +1 8153772599