Jabref used to work on my station. Since March 08, their is a change in antlr ebuild that breaks Jabref. The reason is the nojava use flag was renamed java and enabled by default (using EAPI=1). On my system, this flag is disabled globally. Therefore, Jabref stopped working. The error message given : Package antlr was not found! By running java-check-environment, I got this error message : * Checking package_env ... !!! ERROR: Package antlr was not found! * Broken dependencies for app-text/jabref-2.3 * Please try emerge -uD1 =app-text/jabref-2.3 I followed the given instructions but jabref could not compile because java-support was missing from antlr. I enabled the java use flag and recompiled antlr. Now Jabref works. Jabref should check at build time if java support is enabled in antlr and tell the user to recompile with USE=java if necessary. (see treeviewx as an example) The best solution would be use-deps but these require EAPI=2. Reproducible: Always Steps to Reproduce: 1.run jabref with antlr compiled without the java flag enabled 2.run emerge jabref Actual Results: Solved by recompiling antlr with java flag enabled Expected Results: Problem solved
It's not just jabref, but all in http://tinderbox.dev.gentoo.org/misc/rindex/dev-java/antlr Except net-firewall/fwbuilder which only needs the c++ part, and checks for nocxx flag (should probably be updated to check for cxx flags now that it changed...) So either we update all those ebuilds with the built_with_use check, or just drop the java flag and make it mandatory? Antlr unconditionally depends on a jdk anyway, and nobody seems to have complained yet :)
jabref 2.4.2 use EAPI 2 use deps
