Betelgeuse said he would prefer an EANT_NEEDS_TOOLS variable over a jdk-tools virtual so here's a patch for java-utils-2.eclass. Please add this soon so I can delete the virtual from the overlay.
Created attachment 160252 [details, diff] eant-needs-tools.patch
Is anyone looking at this anymore. I would like to see netbeans with support for ruby as many other users would also. This is a crucial step to moving gentoo forward to be used in a business enviroment.
(In reply to comment #2) > Is anyone looking at this anymore. I would like to see netbeans with support > for ruby as many other users would also. This is a crucial step to moving > gentoo forward to be used in a business enviroment. > In contrast to what the comment in the Netbeans ebuild says tools.jar is actually always put to ant classpath. You can see this by reading /usr/bin/ant. We have been discussing this issue every once in a while and have we don't think we should add support for tools.jar in general. tools.jar is a collection of separate things so we should instead have things like a virtual for javadoc. Then it can be provided also by packages like dev-java/gjdoc.
The last time I tried that, tools.jar was not on classpath when running eant from ebuild. This applies to both netbeans and my attempt to bump jax-ws to version 2.1 (needed to resolve another netbeans bug). tools.jar is available on classpath in case ant is run from command line, iirc, but that's useless for packaging packages that need tools.jar. And if it would be true that "tools.jar is actually always put to ant classpath", there would be no need for this bug nor bug #174182 imo. So the first sentence in comment #3 is not clear to me. If I understand it correctly, I should not get "package not found" error for tools.jar packages while compiling netbeans or jax-ws as "tools.jar is actually always put to ant classpath". Or does that mean that tools.jar is available to ant but not available for the compiled application? Anyway, I need a vorking solution to be able to compile both ruby support in netbeans and jax-ws 2.1.
(In reply to comment #4) > Or does that mean that tools.jar is available to > ant but not available for the compiled application? > Maybe you need to take the Java quiz again :). Ant classpath != javac classpath. Remember that we always use -Dbuild.sysclasspath=ignore nowadays.
(In reply to comment #5) > (In reply to comment #4) > > Or does that mean that tools.jar is available to > > ant but not available for the compiled application? > > > > Maybe you need to take the Java quiz again :). Ant classpath != javac > classpath. Remember that we always use -Dbuild.sysclasspath=ignore nowadays. > Maybe I should :-) Thank you for clarification, now I recall I saw -Dbuild.sysclasspath=ignore somewhere before :-P So to say it correctly, netbeans needs tools.jar on javac classpath to compile ruby cluster, and the same is needed for jaxw-ws 2.1 to compile.
There ya go crybabies, patch added. Remebemer it's just an intermediate solution for build-time dep only, virtuals mentioned in bug #174182 is the right way. But I figured that usage of this variable would be easier to detect and convert later so enjoy. Also realize that you never had to wait for this, you could have always write own src_compile() and call java-config --tools there. Like jedit did. Oh well.
