Pre-mature stabilization request. I just rev-bumped from -r4. This package is badly named it does not reflect that the package is being build from Tomcat sources. 5.5.17 in -r4, and 5.5.20 in -r5. Considering Tomcat uses this package as it's provided servletapi, instead of building and having it's own. Current stable Tomcat 5.5.20 is using a 5.5.17 servletapi. Thus the pre-mature request so we can ensure Tomcat 5.5.20 is really stable, and using the proper version of servletapi. I will be working to correct all this ASAP. Including re-naming and versioning the package so this won't happen again. Otherwise hard to tell the relation amongst the packages and that they are in/out of sync. Thanks
done on x86
ppc stable
Ping amd64 arch team. Stable on both x86 and ppc now. Would like to be on amd64 so I can remove gen 1 versions of the packages. Thanks
Another amd64 ping :). Really need to get this stabilized. The 2.4-r2 that is current stable is using 5.0.x sources. Which in turn Tomcat 5.5.20 uses that, and it's no good. The two need to be in sync sources wise. Working on cleaning up that mess, but in the mean time. Just need amd64 stabilization. Thanky youz :)
Added keyword myself with permission from amd64 arch team. Closing bug since package is stable on all archs that matter now :)
Re-opening since I need ppc64 stable keyword before I can remove previous version of the ebuild, 2.4-r2. Must have forgot that arch when filing bug, much less closing.
ppc64 stable marking as FIXED
