-
1. Re: javassist handling of "unused" import package name
starksm64 Dec 20, 2004 7:55 PM (in response to ben.wang)Import of an unused class will not compile under javac either. We just need to be providing the same clear indication of the problematic import:
[starksm@banshee9100 tmp]$ cat X.java import nopkg.NoClass; class X { } [starksm@banshee9100 tmp]$ javac X.java X.java:1: package nopkg does not exist import nopkg.NoClass; ^ 1 error
-
2. Re: javassist handling of
ben.wang Dec 20, 2004 9:06 PM (in response to ben.wang)I know that, and that's the reason I am saying that different classpaths for javac and aopc (or even runtime).
Sometimes during compilation, you knowingly (or unknowingly) include some classpath that you are not using in one specific runtime. So during runtime, you don't include that specific library in the classpath. And everything will be fine since the code is not used.
But this is not fine under Javassist since it requires access to every import package.
-Ben -
3. Re: javassist handling of
starksm64 Dec 21, 2004 10:48 AM (in response to ben.wang)So what is source of the unused class references, javac putting them into the class file? Create an issue in jira with an example of what your talking about needing to be handled better.
-
4. Re: javassist handling of
ben.wang Dec 21, 2004 2:33 PM (in response to ben.wang)OK, I have created one:
http://jira.jboss.com/jira/browse/JBAOP-56