posted 22 years ago
Well it's definitely not the first scenario, because there are not dependent jars. It seems your second idea is the case. As far as the CLASSPATH issue goes, I don't understand how this would be a problem. Here is my situation:
I have a class with package name com.test.MyClass
My script compiles that class and copies the class file to the com\test directory. Then the script compiles a class with no package name. It just sits at the root. ( I have heard this is bad practice. Is it? ) Anyway, the compiler is not able to find the com.test.MyClass class and complains on the import, thus causing the whole thing to fail. This is just an example. The real application has many packages, and the compiler complains about all of them. The script worked before with 1.3 and there have been no changes except switching to 1.4. So, maybe someone can tell me was I compiling improperly before and it worked anyway or is there a bug in 1.4???
Thanks,
Barry