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...
Best regards, Eric > -----Ursprüngliche Nachricht----- > Von: Barrie Treloar [mailto:[email protected]] > Gesendet: Mittwoch, 19. August 2009 10:15 > An: Maven Users List > Betreff: Re: OSGi compatible dependencies > > On Wed, Aug 19, 2009 at 5:32 PM, Lewis, Eric<[email protected]> wrote: > > 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. > > I think I've posted about this before but not really given it > enough thought. > > I still can't see why if it is not OSGi compliant that the default > position it to make the entire jar packages visible. > Since that's what is happening in an non-OSGi environment anyway. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
