… compile: [javac] Compiling 115 source files to /var/tmp/portage/dev-java/saaj-1.3.19/work/saaj-1.3.19/build/classes [javac] /var/tmp/portage/dev-java/saaj-1.3.19/work/saaj-1.3.19/src/java/com/sun/xml/messaging/saaj/SOAPExceptionImpl.java:46: package javax.xml.soap does not exist [javac] import javax.xml.soap.SOAPException; … [javac] 100 errors [javac] 3 warnings BUILD FAILED /var/tmp/portage/dev-java/saaj-1.3.19/work/saaj-1.3.19/build.xml:159: Compile failed; see the compiler error output for details. Total time: 3 seconds * ERROR: dev-java/saaj-1.3.19 failed (compile phase): * eant failed * * Call stack: * ebuild.sh, line 85: Called src_compile * environment, line 3909: Called java-pkg-2_src_compile * environment, line 1955: Called eant 'jar' '-f' 'build.xml' * environment, line 567: Called die * The specific snippet of code: * ant ${antflags} "${@}" || die "eant failed" * * If you need support, post the output of `emerge --info '=dev-java/saaj-1.3.19'`, * the complete build log and the output of `emerge -pqv '=dev-java/saaj-1.3.19'`. !!! 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.22" JAVACFLAGS="-source 1.5 -target 1.5" COMPILER="javac" and of course, the output of emerge --info I know, sun-jdk-1.5 (which I'm using from the java-overlay) isn't supported anymore, but wouldn't it then be prudent to have the ebuild depend on >=virtual/jdk-1.6? Or otherwise make sure that the jar from dev-java/jsr67 is on the classpath. Obvious workaround: JAVA_PKG_FORCE_VM=sun-jdk-1.6 emerge -1 saaj
Fixed in -r1. Thanks for the report. We still have gcj-jdk which is an 1.5 jdk so if it's reasonably possible having >=1.5, it won't hurt. We have virtuals with jdk providers for exactly this purpose. There was also an upstream bug which made use of 1.6 bcp.
