Found when trying to reproduce that other bug with jarjar, unrelated to it. * Using ecj-3.3 for compilation * Using all available ANT_TASKS Buildfile: build.xml init: [echo] bootclasspath compile: [mkdir] Created dir: /var/tmp/portage/dev-java/jarjar-0.9/work/jarjar-0.9/build/main [copy] Copying 1 file to /var/tmp/portage/dev-java/jarjar-0.9/work/jarjar-0.9/build/main [copy] Copied 5 empty directories to 2 empty directories under /var/tmp/portage/dev-java/jarjar-0.9/work/jarjar-0.9/build/main [javac] Compiling 43 source files to /var/tmp/portage/dev-java/jarjar-0.9/work/jarjar-0.9/build/main [javac] ---------- [javac] 1. ERROR in /var/tmp/portage/dev-java/jarjar-0.9/work/jarjar-0.9/src/main/com/tonicsystems/jarjar/AbstractDepHandler.java (at line 1) [javac] /* [javac] ^ [javac] The type java.lang.Object cannot be resolved. It is indirectly referenced from required .class files Not affected by JAVA_PKG_STRICT. Strangely, ecj-3.2 works fine, so might be a regression in 3.3 that should be investigated as might affect other packages too.
Fixed
