On 17/11/06, Piyush Purang <[EMAIL PROTECTED]> wrote:
Till now I haven't had this problem of direct conflict with java(x).*
packages. Dave are you referring to a sun.* package? Could you please
give a specific example?
Container and java.awt.Container.
Guard, java.security.Guard
Handler, java.util.logging.Handler
MediaType java.awt.PageAttributes.MediaType
Request org.omg.corba.Request
Request org.safehaus.asyncweb.http.internal.Request
best one. Method
Comment out the import.
Resolve imports,
it offers me
java.lang.reflect.Method
com.sun.java.util.jar.pack.package.....
com.sun.org.apche.bcel....
etc etc
I.e.there are lots of them; hence lots of room for error.
I've a few more on paper at home. I'll mail them.
Checkstyle can check for following things for import statements see
http://checkstyle.sourceforge.net/config_imports.html
None of them seems to fit the bill for our usecase.
I have a shell script
for %%f in ("*.jar") do jar -tf %%f | grep32 %1
for windows and convert for Linux.
It will find a class, but the jars need to be in the same directory.
Whether we could feed all the restlet classes... bit like hard work?
Perhaps users on the list could post name conflicts when they come across them?
regards
HTH DaveP
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
