mod_jk has no required dependency on tomcat. To use it, you probably need a tomcat running somewhere, but that tomcat could be running anywhere (i.e. not on the current host). Additionally, you could use mod_jk to talk to Jboss with a bundled tomcat vs. a standalone tomcat. I think this dependency should be removed.
ok, in that case i'll add a warning to pkg_postinst to tell users about it
Hmm, I
Hmm, I´d prefer something like USE="tomcat" ;-)
a useflag with that name is misleading, imho
Why should it be misleading if it emerges tomcat as a dependency? :-) BTW, the default values workers.tomcat_home and worker.ajp13.host (in jk-workers.properties) and jkAutoAlias and jkMount (in 88_mod_jk.conf) no longer make sense if Tomcat is not installed on localhost. Sure, this is a purely cosmetic issue.
I was originally going to suggest a USE flag, but the useflag is misleading. In practice, gentoo developers abuse the USE flags tremendously however. USE flags should only directly impact the package being built. There is nothing about tomcat that is either necessary to build or use mod_jk. All adding a tomcat USE flag would be doing is making mod_jk dependent on tomcat, so that it happens to get installed, which IMO is actually the misleading thing, because there's nothing about mod_jk that requires tomcat in and of itself. I do agree that the default worker and mod_jk.conf files are irrelevant. However, if you're using tomcat to communicate with a remote system, you should be capable of understanding the files and tweaking them, and if you aren't, you can simply emerge tomcat, and the default files will allow things to work. workers.tomcat_home and workers.java_home are pretty much useless properties now so they don't even need to be set. Those properties are used for an inprocess worker, which I believe is either deprecated, or not even implemented in mod_jk anymore. Can't remember which.
fixed in cvs, thanks for the suggestion and for using gentoo. :-)
