The same issue with 2.1.12

jabref-2.6-build.log (text/plain), 3.38 KB, created by Ralph Sennhauser (RETIRED) on 2013-02-08 15:29:59 UTC

Emerging (1 of 1) app-text/jabref-2.6
 * JabRef-2.6-src.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...                                                                             [ ok ]
!!! ERROR: Couldn't find suitable VM. Possible invalid dependency string.
           Due to stax-api requiring a target of 1.7 but the virtual machines constrained by virtual/jdk-1.6 
 * Unable to determine VM for building from dependencies:
NV_DEPEND: virtual/jdk:1.6
	dev-java/spin:0
	|| ( >=dev-java/glazedlists-1.7.0-r1:0 >=dev-java/glazedlists-1.7.0:0[java5] )
	>=dev-java/antlr-2.7.3:0[java]
	>=dev-java/jgoodies-forms-1.1.0:0
	dev-java/jgoodies-looks:2.0
	>=dev-java/microba-0.4.3:0
	dev-java/jempbox:0
	dev-java/pdfbox:0
	dev-java/commons-logging:0
	dev-java/jpf:1.5
	dev-java/jpfcodegen:0
	mysql? ( dev-java/jdbc-mysql:0 ) >=dev-java/java-config-2.1.9-r1   >=dev-java/ant-core-1.7.0
	   
	   
	   >=dev-java/javatoolkit-0.3.0-r2
	   >=dev-lang/python-2.4
 * ERROR: app-text/jabref-2.6 failed (setup phase):
 *   Failed to determine VM for building.
 * 
 * Call stack:
 *             ebuild.sh, line   93:  Called pkg_setup
 *             ebuild.sh, line  326:  Called java-pkg-2_pkg_setup
 *     java-pkg-2.eclass, line   53:  Called java-pkg_init
 *   java-utils-2.eclass, line 2187:  Called java-pkg_switch-vm
 *   java-utils-2.eclass, line 2671:  Called die
 * The specific snippet of code:
 *   					die "Failed to determine VM for building."
 * 
 * If you need support, post the output of `emerge --info '=app-text/jabref-2.6'`,
 * the complete build log and the output of `emerge -pqv '=app-text/jabref-2.6'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
 * The complete build log is located at '/tmp/portage/app-text/jabref-2.6/temp/build.log'.
 * The ebuild environment file is located at '/tmp/portage/app-text/jabref-2.6/temp/die.env'.
 * Working directory: '/tmp/portage/app-text/jabref-2.6'
 * S: '/tmp/portage/app-text/jabref-2.6/work/jabref-2.6'

>>> Failed to emerge app-text/jabref-2.6, Log file:

>>>  '/tmp/portage/app-text/jabref-2.6/temp/build.log'

 * Messages for package app-text/jabref-2.6:

 * Unable to determine VM for building from dependencies:
 * ERROR: app-text/jabref-2.6 failed (setup phase):
 *   Failed to determine VM for building.
 * 
 * Call stack:
 *             ebuild.sh, line   93:  Called pkg_setup
 *             ebuild.sh, line  326:  Called java-pkg-2_pkg_setup
 *     java-pkg-2.eclass, line   53:  Called java-pkg_init
 *   java-utils-2.eclass, line 2187:  Called java-pkg_switch-vm
 *   java-utils-2.eclass, line 2671:  Called die
 * The specific snippet of code:
 *   					die "Failed to determine VM for building."
 * 
 * If you need support, post the output of `emerge --info '=app-text/jabref-2.6'`,
 * the complete build log and the output of `emerge -pqv '=app-text/jabref-2.6'`.
 * The complete build log is located at '/tmp/portage/app-text/jabref-2.6/temp/build.log'.
 * The ebuild environment file is located at '/tmp/portage/app-text/jabref-2.6/temp/die.env'.
 * Working directory: '/tmp/portage/app-text/jabref-2.6'
 * S: '/tmp/portage/app-text/jabref-2.6/work/jabref-2.6'
 * 
 * The following package has failed to build or install:
 * 
 *  (app-text/jabref-2.6::gentoo, ebuild scheduled for merge), Log file:
 *   '/tmp/portage/app-text/jabref-2.6/temp/build.log'
 *