The problem is that the build.sh called by the ant ebuild doesn't exit with an error
code when there is a probem. The problem I had was that JDK_HOME wasn't in
my enviroment so JAVA_HOME got set to an empty string. If the ebuild die'ed
on an empty JDK_HOME that would at least alert the user to a problem.
need some "|| die"s?
I'd say adding:
[ -n "$JDK_HOME" ] || die "Java JDK not properly installed. Please (re)install."
to the top of the src_compile() function would be enough.
Since it depends on virtual/jdk-1.3, the environment should be setup correctly.
However, maybe when an older jdk package is installed that didn't use the new
java scheme yet, this dep is resolved but the required env var is not present.
Is this possible?
Yup, The enviroment was set up correctly when I re-emerged the jdk I was using.
I guess I should use -rX on virtual deps, too, to avoid this problem. If this
bug gets reopened later, I will bother :)