The tomcat 6 porting work was done on F12. Apparently the jars in F13 introduced a new dependency on /usr/share/java/jakarta-commons-lang.jar in the jakarta-commons-lang rpm. Rather than adding yet another jar symlink in pkicreate and waiting for next jar problem to pop up I'm proposing a solution which frees us from explicitly managing jars in our tomcat instances. The proposal has been sent to the team for review. I'm attaching the patch which implements it here. After the proposal has been reviewed I will attach it to this bugzilla.
Created attachment 464046 [details] Eliminated explicit jar management, use common classloader path
Created attachment 464425 [details] fix link creation in pkicreate Fix symbolic links to jars jakarta-commons-lang.jar is needed by velocity, add that link in WEB-INF/lib. This dependency first appeared in F13. We had been providing a link to jakarta-commons-collections.jar in $pki_instance/common/lib but that link is not necessary since tomcat6 already provide jakarta-commons-collections.jar. So remove the superfluous link creation, it isn't needed. Note, we don't have consensus yet on how to address jar dependencies so this patch should be applied now, it's consistent with how we've been doing things. The previous patch was just a demonstration example of an alternative approach. This is the patch which needs to be applied so the tip works on F13.
Sending base/setup/pkicreate Transmitting file data . Committed revision 1602.