Yes, but in an OSGi environment it makes it pretty much useless, I think.
Having every package public would be the "quick'n'dirty" solution, but IMHO the
better solution would be the real separation of API and Implementation in the
JAR by the authors. Of course, this takes time and effort...
Bes
Hi
I know just a little bit about OSGi :-)
About 1)
This isn't possible, since the OSGi Manifest states what packages are visible
for the user of the JAR. You can't automate that, it has to be planned by the
authors.
On the other hand, a lot of Apache Commons projects already build OSGi
comp
