As a consumer, I have no trouble having a single, potentially larger than necessary bundle, rather than several that I have to manage. And when it comes time for an upgrade, I’m happy to know that I don’t have to dedicate a portion of a day figuring out what needs to be removed, to prevent version collision issues.
Related to the leakage issue, it seems to work better for me to have separate bundles for widely used open source, but the convenience of having a self-contained and relatively complete bundle is appealing, just so long as there’s no leakage. BTW, usage does tend to winge a bit about the multiple sources of particular bundles. So far I’ve been able to ignore the complaints. Mark > On Nov 5, 2014, at 7:13 AM, Andy Seaborne <a...@apache.org> wrote: > > What I (still) don't understand is the use case for separate bundles per > separate jena module. (not that I'm an OSGi user ATM) > > The contract around a Jena release is that the whole thing works together. > There aren't independent releases of ARQ and core, say. It has been done as > independent jars a while ago but the net result was just version confusion. > That's also why they have the same version numbers nowadays. The separation > of modules is "internal" rathe rthan an external contract. > > And yet people still manage to create mixed up combinations of jars so I > wonder if the main jar ought not to be one combined jena jar (c.f. > apache-jena-libs except that's a POM). Keep the dependencies separate. > > Is there a real need for separate jena-* nowadays? Or is it just a source of > confusion and mistakes? > > Andy > > > On 04/11/14 10:54, Reto Gmür wrote: >> Hi >> >> In the clerezza project we have been wrapping jena for a while as OSGi >> bundles. >> >> Recently it got split up into different bundles. The source (i.e. the poms) >> can be seen here: >> >> https://github.com/apache/clerezza/tree/master/ext >> >> Cheers, >> Reto >> >> On Sat, Nov 1, 2014 at 2:26 AM, Stian Soiland-Reyes < >> soiland-re...@cs.manchester.ac.uk> wrote: >> >>> I would like to hear from your experience of a custom-wrapped bundle >>> what you decided to include or not. >>> >>> See my other email message in this thread.. >>> >>> Basically in short: >>> >>> >>> http://build.mygrid.org.uk/ci/job/jena-bundle/21/org.apache.jena$jena-osgi/ >>> >>> >>> http://repository.mygrid.org.uk/artifactory/ext-snapshot-local/org/apache/jena/jena-osgi/2.12.2-SNAPSHOT/ >>> >>> http://repository.mygrid.org.uk/artifactory/ext-snapshot-local/org/apache/jena/jena-parent/12-SNAPSHOT/ >>> >>> >>> >
