Attempting to emerge mod_jk results in (attempted) emerge of a java VM (blackdown by default, but its irrelevant to the problem). Simply: mod_jk does NOT need any JRE/JDK installed. Consider the use case where the machine in question is running Apache, and is connecting to Tomcat which resides on a /different/ host. In such a case, there need not be any Java environment on the Apache host, and there is no reason to install one just becasue you want to connect Apache through to Tomcat on a different host. Ebuild patch attached.
Created attachment 70555 [details, diff] Proposed patch to mod_jk-1.2.13.ebuild Not sure if I've done this "right" - is it OK to just delete the DEPEND line or should I have done something else. (Insufficient experience with ebuilds!)
DEPEND="" would be the right way to go. Fixed in portage, thanks for reporting.
(In reply to comment #2) > DEPEND="" would be the right way to go. Fixed in portage, thanks for reporting. > Any idea why this dependency was reintroduced in mod_jk-1.2.27? >= mod_jk-1.2.27 ebuilds now contain: DEPEND=">=virtual/jdk-1.4"
The dpendency still exists in 2015 and forces users who want to avoid a jdk on a frontend machine to use apache/mod_proxy.
