This happens on two different machines. So I'm assuming it's a bug. The full error message follows. Will attach emerge --info immediately. # emerge --oneshot jarjar Calculating dependencies... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) dev-java/jarjar-0.6-r1 to / * jarjar-src-0.6.zip RMD160 ;-) ... [ ok ] * jarjar-src-0.6.zip SHA1 ;-) ... [ ok ] * jarjar-src-0.6.zip SHA256 ;-) ... [ ok ] * jarjar-src-0.6.zip size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking jarjar-src-0.6.zip ;-) ... [ ok ] * Using: sun-jdk-1.5 >>> Unpacking source... >>> Unpacking jarjar-src-0.6.zip to /var/tmp/portage/dev-java/jarjar-0.6-r1/work >>> Source unpacked. Rewriting source attributes Using Sax to rewrite the build.xml files Rewriting ./build.xml Rewriting target attributes Using Sax to rewrite the build.xml files Rewriting ./build.xml Rewriting nowarn attributes Using Sax to rewrite the build.xml files Rewriting ./build.xml >>> Compiling source in /var/tmp/portage/dev-java/jarjar-0.6-r1/work/jarjar-0.6 ... * Using all available ANT_TASKS Buildfile: build.xml init: compile: [mkdir] Created dir: /var/tmp/portage/dev-java/jarjar-0.6-r1/work/jarjar-0.6/build/main [copy] Copying 2 files to /var/tmp/portage/dev-java/jarjar-0.6-r1/work/jarjar-0.6/build/main [copy] Copied 6 empty directories to 1 empty directory under /var/tmp/portage/dev-java/jarjar-0.6-r1/work/jarjar-0.6/build/main [javac] Compiling 53 source files to /var/tmp/portage/dev-java/jarjar-0.6-r1/work/jarjar-0.6/build/main jar: [mkdir] Created dir: /var/tmp/portage/dev-java/jarjar-0.6-r1/work/jarjar-0.6/dist [jarjar] Building jar: /var/tmp/portage/dev-java/jarjar-0.6-r1/work/jarjar-0.6/dist/jarjar-0.6.jar BUILD FAILED /var/tmp/portage/dev-java/jarjar-0.6-r1/work/jarjar-0.6/build.xml:70: java.lang.NullPointerException Total time: 8 seconds !!! ERROR: dev-java/jarjar-0.6-r1 failed. Call stack: ebuild.sh, line 1632: Called dyn_compile ebuild.sh, line 983: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile ebuild.sh, line 1322: Called java-pkg-2_src_compile java-pkg-2.eclass, line 84: Called eant 'jar' '-f' 'build.xml' java-utils-2.eclass, line 1894: Called die !!! eant failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/dev-java/jarjar-0.6-r1/temp/build.log'. !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.12" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="javac" and of course, the output of emerge --info
Created attachment 126852 [details] emerge --info
Does 0.9 work? It's time for it to go stable any way.
jarjar-0.9 complains about a missing java-getopt-1 package. After installing java-getopt both jarjar-0.6-r1 and jarjar-0.9 emerge fine. Adding a dependency to java-getopt would solve this.
(In reply to comment #3) > jarjar-0.9 complains about a missing java-getopt-1 package. After installing > java-getopt both jarjar-0.6-r1 and jarjar-0.9 emerge fine. > > Adding a dependency to java-getopt would solve this. > Woot? The dep is there: pena jarjar # emerge -pvt jarjar These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild N ] dev-java/jarjar-0.9 USE="-doc -source -test" 0 kB [0] [ebuild N ] dev-java/gnu-regexp-1.1.4-r2 USE="-doc -source" 161 kB [0] [ebuild NS ] dev-java/asm-2.0-r1 USE="-doc -source" 253 kB [0] [ebuild N ] dev-java/java-getopt-1.0.13 USE="-doc -source" 45 kB [0]
Oops, you are right, sorry. I used --nodeps for speed reasons which was a mistake in this case. So dependency to java-getopt seems to be missing in 0.6-r1 but is ok for 0.9. So, I would also suggest to mark 0.9 stable. If so, this bug can be closed.
(In reply to comment #5) > > So, I would also suggest to mark 0.9 stable. If so, this bug can be closed. > stable now
