Mmmh, that is right producing binary bundles is the way forward. Then one would need maven to download these bundles and place them into an Eclipse Target Platform structure. Not sure there already exists such a maven plugin, maybe the Geronimo stuff is suited?
Right now the easiest way for me is just to use the Eclispe "Create Plugin from extisting JAR" wizard, but that ends up in a wrapper bundle in the workspace, which is not optimal. Anyone knows if there is a maven plugin to generate an Eclipse target platform from a POM? /peter On 10/5/06, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Thursday 05 October 2006 15:30, Peter Neubauer wrote: > > > in order to develop in eclipse, it is very convenient to wrap needed > > jars into library bundles and have them directly in the workspace or > > in some target platform location. Now, this Eclipse specific and would > > contain jar files inside the bundle projects, so I wonder what the > > best place would be to place them in, e.g. some lib bundles in order > > to get the Pax projects running inside Eclipse? > > Are we talking the "project" of Osgifying 3rd party libs into bundles, or > something else? > > If the former, then I suggest; > projects/pax/libraries/ > > because I think the output is generally suitable for everyone. > > OTOH, this will overlap with work at Felix and possibly other places :o(, but > perhaps we can merge the efforts as they start build up. > > > My personal take is that each such should replace the Manifest with the Osgi > entries and re-publish as same group, artifact and version with a 'osgi' > marker (for instance the "classifier" in Maven lingo), and not 'wrap' the > jars, to save both performance and memory in runtime. > > > Cheers > Niclas > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
