With a bnd properties file you should be able to do it right, I just wanted to note that without such additional instructions the result will probably not be very good.
On 27 January 2012 14:04, Alin Dreghiciu <[email protected]> wrote: > The plugin supports an bnd properties file (the recipe) in the same > spot as the jar to be osgi-fyed. That file can be used to fully > customize the generated manifest, such the version. > If you have something in mind let me know to see how we can get it > done correctly. > > On Fri, Jan 27, 2012 at 3:51 PM, David Bosschaert > <[email protected]> wrote: >> On 27 January 2012 13:07, Alin Dreghiciu <[email protected]> wrote: >>> Did you guys considered using >>> https://docs.sonatype.org/display/Nexus/Nexus+OSGi+Experimental+Features+-+Bundle+Maker >>> I wrote an email some months ago about it on this list. Basically the >>> result is the same. It generates the bundles on the fly based on an >>> autogenerated recipe or on a custom made one for cases when default is >>> not enough. >> >> Just to note that I think that auto-bundelizing an existing jar is >> nearly impossible to get right if you want to do the versioning >> properly. >> I think you nearly always need to have some metadata as input to the process. >> >> Cheers, >> >> David >> >> _______________________________________________ >> general mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/general > > > > -- > Alin Dreghiciu > Software Developer > My profile: http://www.linkedin.com/in/alindreghiciu > My blog: http://adreghiciu.wordpress.com > http://sonatype.com - Sonatype - The Maven Company > http://www.ops4j.org - New Energy for OSS Communities - Open > Participation Software. > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
