Hi Rick! Thanks for the anwere, in the official OSGi documentation I only found automated import for java.* packages but not for sun.com. Thus the question. Those imports are done in javassist which performs low level ClassLoader manipulation stuff. So I fear it wont be easy to remove those dependencies.
LieGrue, strub --- On Thu, 7/8/10, Rick McGuire <[email protected]> wrote: > From: Rick McGuire <[email protected]> > Subject: Re: OSGi handling of com.sun.jdi.* packages? > To: [email protected] > Date: Thursday, July 8, 2010, 11:50 AM > On 7/8/2010 7:32 AM, Mark Struberg > wrote: > > Hi! > > > > Do we need to exclude com.sun.jdi.* packages in our > OSGi Bundles and will those packages be provided by default, > or do we need to resolve them as optional? > > > The Geronimo OSGi framework includes all com.sun.* classes, > so these should be available. However, the best > approach would be to eliminate dependencies on com.sun.* > packages entirely, since those by definition are > non-portable. This might preclude using your code on > other JREs, such as Harmony or the IBM J9 version. If > they can't be eliminated, then I'd recommend making them > optional packages and dealing with the classes dynamically. > > Rick > > > txs and LieGrue, > > strub > > > > > > > > > > > >
