Thanks Tim. I've checked in the manifest changes for auth. I've also been looking at jndi's dependency on awt (applet). I think it's a similar situation, in that none of the applet code is reached unless the user has actually tried to instantiate an applet (see org.apache.harmony.jndi.internal.EnvironmentReader.readAppletParameters(..)), so again I don't think we need to do any work here apart from change the manifest to mark those dependencies as optional. I will do that later today unless anyone objects.
2008/12/18 Tim Ellison <[email protected]>: > Sian January wrote: >> I've been looking at the dependency from the auth module to awt, but I >> don't think there's any work to be done there, except to change the >> awt dependencies in the MANIFEST.MF to be optional. >> There is only one class that depends on awt >> (org.apache.harmony.auth.callback.DialogCallbackHandler), and I >> believe for it to be instantiated a user would have to specify its >> name via the auth.login.defaultCallbackHandler security property. If >> that's right, then I think we could just assume that that won't/can't >> be used if awt isn't installed. >> I don't think it makes sense to move the class itself to awt as that >> would introduce a dependency from awt-auth that doesn't already exist. >> >> Does that sound ok? > > +1 > > Tim > -- Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
