the ant script used to start the ant application for compiling java web applications failed to listen to exported JAVA_HOME. Whilst it can operate happily with emerged java versions I need to use an older version which portages does not support. For this reason I export JAVA_HOME to point to this older version. The ant script was modified to read this variable, but I then got library version errors so I have left this to the package developer who better understands. Perhaps this could be moved to java-config supporting custom java installs?
Moving this again to java@gentoo.org, so everyone out there can help.
From the forum, I'm not sure if this thread is actually useful, but it might be... I have found my problem. In fact, in the portage install script, in src_compile() the first line is export jAVA_HOME=${JDK_HOME} And I don't have any JDK_HOME variable (which is not in the official JDK installation). (is it normal ?) So, creating the JDK_HOME variable just before launch emerge jboss solve the problem. I just used the mentioned method (the JDK_HOME) to fix my problem with updating ant. What I'm wondering about is how come this hasn't been fixed? Seems strange to me that "ant" complains about JAVA_HOME not being set correctly, when what it actually means is JDK_HOME.
That's odd, I think your config settings must've gotten messed up somewhere. What was the output of java-config -P <yourjdk> It should list the JDK's home and what not. I'm going to leave this one as resolved unless you can tell me another reason for it not to be.
