On Mon, 2007-03-12 at 13:57 -0400, Yoav Shapira wrote: > > It's a build environment thing. Ya gots to have the JavaMail and > JavaActivationFramework jas on your build classpath (in whatever libs > directory you chose to use in build.properties), or the JNDI mail > session factory won't get built, and thus it won't get bundled in the > distro. > > We should probably add a runtime class check (Ant <available > classname=.../>) to the "release" Ant target that fails the build if > that class isn't present. That way we'll be sure to never have this > issue come up again.
Those core optional dependencies or etc were/are a pita. Thus we have tons of dependencies I was never sure if they were needed or did anything on Gentoo. Due to lack of time, we have just always included all. Now it's good to find out they do activate/limit functionality within Tomcat. Further justifies their presence, or us including all optional packages during Tomcat build process. In fact we have dropped some like jmx/mx4j if a >=1.5 jdk is used since it's present in the jdk. However it seems to have caused some very odd bug in catalina.jar. That only shows up when working with the manager app. I believe it was deploy app via manager app, restart tomcat, and then try to undeploy, to replicate problem. But only when Tomcat is built with >=1.5 as bytecode 1.5, and some dropped dependencies. Jars not present at compile time. So seeing how another bug is caused when javamail and etc are not present. Then it might also explain the other bug in catalina.jar. -- William L. Thomson Jr. Gentoo/Java
signature.asc
Description: This is a digitally signed message part
