- compiles in src_install - doesn't do error checking - doesn't use dojar - chown's /etc/{init.d,conf.d}/jetty and /etc/jetty to jetty:jetty i was slapped by security when it was like that in tomcat (only user has write premissions tho, not the group)
Created attachment 58795 [details] jetty-4.2.19-r1.ebuild * Declares and uses MY_PN and MY_P * Added dependencies to java packages that jetty uses (that are in portage) * Added RDEPEND of jre (but it may need the java packages too) * Now uses jikes and doc * Included a patch for jikes, and to gentooification * Uses external jars through a build.properties * Now uses java-pkg_dojar * Cleaned up the install, using PN and JETTYHOME where they could be, fixed permissions and owernship of /etc files
Created attachment 58796 [details, diff] jetty-4.2.19-jikes.patch Fixes all errors and some warnings caused by using jikes.
Created attachment 58797 [details, diff] jetty-4.2.19-gentoo.patch Cleans up the build.xml, and allows us to use build.properties to define where jar files are located. Also a minor fix in ${S}/bin/jetty.sh... changes head -1 (which is deprecated and causes output to stderr) to head -n 1
Created attachment 58798 [details] jetty-4.2.24-jikes.patch Version bump for the 4.2 series of jetty. There also seems to be a 5.1 release as well which they have marked 'stable'. Note: it is necessary to cp -r ${FILESDIR}/4.2.19 ${FILESDIR}/4.2.24 jetty-4.2.19-gentoo.patch applies cleanly, but a different patch is needed for jikes.
Created attachment 58799 [details] jetty-4.2.24.ebuild Accidentally attached the jikes patch when I meant to attach the ebuild... Sorry for the confusion.
Created attachment 58804 [details] jetty-4.2.24.ebuild * Added use flags: source, junit, and extra (the extra webapps) * Removed jars from ${S}/ext. Patched jetty.sh to reflect this * Cleans out ${S} before it is copied to ${D}/${JETTY_HOME} (ie, removes src if !source, classes, and so on)
I think I may have broken the most recent ebuild by deleting ${S}/ext, seeing as jasper-compiler.jar and jasper-runtime.jar aren't provided by a package in portage (yet). I had posted the jikes patches I made to project's sourceforge page, and the response I got from a developer was: "I think both of these have been fixed in Jetty 5. If you are doing a new package, then I really think that Jetty 5 (the stable release) should be the target." So that being said, perhaps this bug should be closed in favor of #68082 which is working on jetty-5.1.1.
*** Bug 94450 has been marked as a duplicate of this bug. ***
While its good this is a compile from source version. It's for an older version and pretty sure any focus these days would go to 5.x or 6.x. Going to close this bug as wontfix for now. If someone needs this version we can re-open. There are bugs open already for 5.x bug 68082 and 6.x bug 147469
