Summary: | mod_jk2 official unsupported by Apache, now | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | tuXXer <bs.net> |
Component: | Current packages | Assignee: | Jan Brinkmann (RETIRED) <luckyduck> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | apache-bugs, java, m.debruijne, menion |
Priority: | Normal | ||
Version: | 2004.3 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
tuXXer
2005-01-13 06:52:39 UTC
I agree. when this is "officially" unsupported by apache, is there any need for this package anyway? If not, it would make *NO* sense in porting it to the new apache-module eclass. reassigning to /me cause i'll start maintaining tomcat. i'll work on the mod_jk as far as i've got tomcat itself cleaned up and working. i think i'll focus on the 5.5x release first and afterwards i'll work on the 5.0.x release. i'm not sure about the 4.0 version yet. So is mod_jk2 abandoned? Should I switch back to mod_jk? I have an ebuild for GroupWise WebAccess and I need to update it to work with something. Can someone give me some official advice? yep. mod_jk2 is deprecated, i'm not sure if we'll remove this version from the tree soon but a better solution would it be to use the mod_jk instead since that project is activly maintained and developed upstream. Since mod_jk2 will not be used, removing the block on the apache package refresh. for everybody who still uses the mod_jk2 , i'm going to remove it from the tree on sunday evening. i'll add mod_jk either tonight or tomorrow, depends on various things. marking this one as fixed. |