Red Hat Bugzilla – Bug 158734
eclipse-ecj-3.1.0_fc-0.M7.5 breaks java-gcj-compat's tools.jar
Last modified: 2007-11-30 17:11:06 EST
Description of problem: Changes to com.sun.tools.javac.Main in the latest java-1.4.2-gcj-compat break ant's javac task. Version-Release number of selected component (if applicable): java-1.4.2-gcj-compat-devel-1.4.2.0-40jpp_24rh eclipse-ecj-3.1.0_fc-0.M7.5 libgcj-4.0.0-8 How reproducible: Always Steps to Reproduce: 1. javac -classpath /usr/lib/jvm/java/lib/tools.jar Test.java 2. java -classpath /usr/lib/jvm/java/lib/tools.jar:. Test Actual results: java.lang.ClassNotFoundException: org.eclipse.jdt.internal.compiler.batch.Main Expected results: Nothing happens (it Just Works)
Created attachment 114820 [details] Testcase
Ok, the problem is that /usr/share/java/jdtcore.jar was renamed as org.eclipse.jdt.core_3.1.0.jar between eclipse-ecj-3.1.0_fc-0.M6.22 and M7.5. As an immediate fix I'm going to patch java-gcj-compat's tools.jar to use the new path (Beehive will be broken until we do this) but for the long term we should probably do something more robust: a filename like org.eclipse.jdt.core_3.1.0.jar is obviously not something that's going to stay the same over time. How about having having the /usr/share/java symlink called eclipse-ecj.jar? jdtcore.jar is fairly undescriptive for such a crucial file.
Sorry I didn't notice this change when we pushed in Eclipse 3.1M7. eclipse-ecj.jar sounds good to me; I'll make that change now.
java-1.4.2-gcj-compat-1.4.2.0-40jpp_25rh in dist-fc4-HEAD is pointing at org.eclipse.jdt.core_3.1.0.jar, so ant in beehive will start working again when someone moves that across to dist-fc4. If you build a new eclipse for FC4 then could you please make sure java-gcj-compat is updated and rebuilt too? The bit that needs changing is in java-gcj-compat-bz158734.patch for now.
This is fixed in java-1.4.2-gcj-compat-1.4.2.0-40jpp_26rh.
Woah, Andrew hasn't changed it in eclipse yet!
The updated eclipse is building right now.