Hello,
I have a question how others are dealing with this problem when
generating bundles for 3rd party libs.
In the moment I am using Maven 2 for my builds and for example hibernate
as a dependency which
I include in my Maven pom file. As we all know about Maven's transitive
dependency handling this will also provide
all dependencies hibernate has automatically - additionally I will get a
nice .classpath file for Eclipse when
executing mvn eclipse:eclipse.
Now I want to change from the non OSGi hibernate jar file to a hibernate
OSGi bundle.
I therefore execute the pom file from Felix commons and get a new
hibernate jar file - now with a
generated Manifest file but of course without a pom file.
I now - when installing the hibernate bundle in my Maven repository -
can generate a pom file with
-dgeneratePom=true but this pom file will not include any of hibernate's
dependencies.
Now I have several possibilities:
1. stick with the generated pom file and let the developer using
hibernate.osgi figure out which dependencies
he has to add. (the hibernate dependencies of course have been
"osgified" as well and are available in the
Maven repository),
2. use the original hibernate pom file with hibernate.osgi, therefore
using hibernate with its "native" dependencies,
3. write a new pom file for hibernate that includes the bundle
dependencies,
4. see the build environment and the OSGi runtime completely separated,
meaning that for building with Maven I use
the "normal" hibernate jar and its dependencies and for integration
I use the bundled jars within the OSGi runtime.
Thanx in advance for any input, help, recommendations...
Michael
