Erik Bengtson wrote:
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.
This is sort of a loaded question, but in general I would say that your
dependencies should not be on a bundle at all, but on the packages that
your bundle needs. Then any number of bundles can satisfy the dependency.
Aside question, can you give a light on the relationship between OBR and Maven 2
repos and future?
Hard to say. OBR is specifically geared toward resolving OSGi
dependencies, thus it is better suited to dealing with package
dependencies, service dependencies, bundle dependencies, platform
dependencies, etc. Currently, the Maven dependency model is not
sufficient for OSGi dependency resolution. It might be nice if they
could be brought closer together and there has been some discussion in
that area, but we are all busy with other things.
At a minimum, we hope to get Maven generating OSGi bundle metadata,
which would simplify many things.
-> richard
