This builds tomcat5 from source then installs it. There may be bugs there may be syntax errors, at present jsvc needs to be made to with tomcat and its build process improved (slightly) to reduce unecessary rebuilding of servletapi-2.4 It also changes the tomcat users hsell from /bin/bash to /bin/false ... I have noticed no side effects from this TYhis build requires others beware! Reproducible: Always Steps to Reproduce:
Created attachment 23624 [details] Ebuild for tomcat5
Created attachment 23625 [details] Da Changelog updated
Created attachment 23626 [details, diff] Fixes some minor build stopping issues
Created attachment 23627 [details, diff] Essentially the same as the gentoo patch for previous tomcats
Created attachment 23652 [details] My Ebuild for struts There is already an ebuiild for struts, it works just need to check that tomcat5 build and the bugzilla struts play ball for now here is the one i used
there is one important thing about part of the the patch i did to setclasspath.sh: JAVA_ENDORSED_DIRS="${JAVA_HOME}/lib:${BASEDIR}/common/endorsed" without adding "${JAVA_HOME}/lib" to JAVA_ENDORSED_DIRS the fol- lowing testpage will not work due to an compiler error, which is actually NOT an compiler error but missing some classes from "tools.jar", which is located at ${JAVA_HOME}/lib: http://localhost:8080/jsp-examples/jsp2/misc/config.jsp perhaps you find a better solution... andre
I am seein g this back at me JSP 2.0 Examples - JSP Configuration Using a <jsp-property-group> element in the web.xml deployment descriptor, this JSP page has been configured in the following ways: * Uses <include-prelude> to include the top banner. * Uses <include-coda> to include the bottom banner. * Uses <scripting-invalid> true to disable <% scripting %> elements * Uses <el-ignored> true to disable ${EL} elements * Uses <page-encoding> ISO-8859-1 to set the page encoding (though this is the default anyway) There are various other configuration options that can be used. This banner included with <include-coda> I am assuming this is correct behaviour which give me a pause for thought as the patch or change that was suggested by andre seem to have no impact or bearing on my configuration, However if it remains to be a poroblem foir others then I will happly change the patch, nice to know people are testing this monster out
You may want to investigate java-pkg_jar-from in the java-pkg eclass instead of find_pck. However, it does not currently add to build.properties, it merely symlinks the jar files into the current dir: # cd lib/ ; java-pkg_jar-from commons-cli || die "Failed to find commons-cli"
I think I may have investigated that option, I might try re-writing this build over the next week or so as its a bit of a monster (and can probably be much improved upon) ... also I am sure that tomcat 5 has gone through a few new versions so it probably needs a bump However the other build services this so I am left wondering, does this build need updating or retireing (I initally built it as i needed tomcat 5 outright and to scratch a personal itch to see how easy it was to build from source)
I guess an update is sufficient. However, I would urge you to submit a fresh ebuild request, as the upstream authors have updated tomcat to 5.0.25 by now. I'm closing this as WONTFIX, for lack of a SUPERCEDEDBYTOBESUBMITTEDEBUILD;)