Hi, What is the best practice regarging dependencies? For instance, we have some bundles with dependency to commons-dbcp, commons-pool, etc.. Those are currently not in the repository, however I suppose they will eventually be. Meanwhile, should be have a dependency to org.apache.commons_pool/org.apache.commons_dbcp bundles or libraries?
If the best practice is dependency to a bundle, what is the appropriate bundle ids / version? We do not distribute commons bundles/libraries and we would expect users to create their own until available in the repository. Aside question, can you give a light on the relationship between OBR and Maven 2 repos and future? Thanks, Erik Bengtson Quoting Jeff McAffer <[EMAIL PROTECTED]>: > We already do. The entire Eclipse Callisto update site (several hundred > bundles) is available through OBR. Query for "eclipse" at > http://bundles.osgi.org/Main/Repository > > Jeff > > > > > Didier Donsez <[EMAIL PROTECTED]> > 09/10/2006 08:13 AM > Please respond to > felix-dev@incubator.apache.org > > > To > felix-dev@incubator.apache.org > cc > > Subject > Orbit > > > > > > > Jeff McAffer wrote: > > >... The Eclipse community is in the > >process of creating the "Orbit" project > >(http://eclipse.org/proposals/orbit/). > > > >... Without seeking > >to start the technical discussion here in this thread, I am thinking of > >issues like > > - bundle symbolic name conventions > > - version numbering > > - use of nested jars > > - bundling libraries that are actually multiple jars (i.e., is > the > >rule one bundle per JAR) > > - ... > > > > > Do you plan to have a representation compliant with the OBR v2 service ? > > Regards > > Didier > > > >