The dist.xml file of tc6.0.x and of trunk contains a target named "build-webapps-precompile".
It performs precompilation of two web apps: ROOT and examples. This target is not called during release process, and actually it does not work as is: it references non-existent libraries and non-existent subdirectories (like /common/lib, /server/lib). I've prepared a patch to enable this target, but then I thought: what is the benefit from enabling this feature? Regarding the root application: in trunk it does not have the index.jsp, but only index.html, so precompilation makes sense for tc6.0 only. . Does anyone have good points in favor of precompiling those two apps? Otherwise I'll propose removal of that "build-webapps-precompile" target from dist.xml of 6.0 and trunk. Or I can enable precompilation of ROOT app in 6.0 and remove this target from trunk, thus skipping the examples. (If anyone is interested, I've put the current versions of my patches that enable that target here: http://people.apache.org/~kkolinko/patches/2009-07-02_tc6_precompile.patch http://people.apache.org/~kkolinko/patches/2009-07-02_tc7_precompile.patch The patch for tc6 is incomplete: compiled ROOT/index.jsp is not included into the distributives. For trunk that does not matter) Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
