Jetty 5.0.0 has been released (http://sourceforge.net/project/shownotes.php?release_id=266966) and it might be nice if Gentoo supported it. If I get a chance, I'll try and come up with an ebuild, but I wanted to log this as a placeholder at least.
Well Jetty 5.1.0 is out, yet
Created attachment 47633 [details] www-servers/jetty/jetty-5.1.1.ebuild
Created attachment 47634 [details] www-servers/jetty/files/5.1.1/jetty.conf
Created attachment 47635 [details] www-servers/jetty/files/5.1.1/jetty.etc
Created attachment 47636 [details] www-servers/jetty/files/5.1.1/jetty.init
Created attachment 47637 [details] www-servers/jetty/files/5.1.1/jetty.patch
Adding an experimental source Jetty ebuild for version 5.1.1. Have tried to make it as much comfortable as possible. Ebuild works for me. Try it and make it better...
*** Bug 63244 has been marked as a duplicate of this bug. ***
just closed the old bug since we don't need to bugs which tell us the same. your ebuild looks good, the only problem is that you use packed jars. we need an proper tomcat ebuild which makes it possible for us to use java-pkg_jar-from tomcat-5 for example to make use of the jars in other ebuilds. you should also use java-pkg_dojar to install jetty's jar files. they're needed by other packages.
OK, changing to java-pkg_dojar as soon as possible. With the proper tomcat ebuild. Which handling do you suggest? Freezing Jetty ebuild as long as this is the case or publishing it when changed to java-pkg_dojar and make the changes later?
Created attachment 48880 [details] www-servers/jetty/jetty-5.1.1.ebuild Removing symlinks, lib and ext directories. No pointing libs to /usr/share... because of java-pkg_dojar
Created attachment 48881 [details] www-servers/jetty/files/5.1.1/jetty.patch Removing symlinks, lib and ext directories. No pointing libs to /usr/share... because of java-pkg_dojar
Created attachment 48882 [details] www-servers/jetty/files/5.1.1/jetty.init
Tested fine here! Had to USE="-junit" due to other apps on port 8080 and tests failing - but shouldn't be a problem for most.
Created attachment 58938 [details] /jetty-5.1.1-r1.ebuild I have a couple improvements: * Added dependency to mx4j, and use jars from that instead of packed jars * Cleaned up DEPEND a bit, specifically consolidated all the extra? together * Added note that extra/ext/activation.jar can be provided by sun-jaf-bin and gnu-activation, but I'm not sure which should be used. * In src_compile, changed it so you can make javadoc and/or do unit tests. * In src_install, now it only does dojar for jar files in lib/. The ones in ext/ are provided somewhere else already, and start/stop.jar are just used to start and stop the server. On a different note, is it really necessary that jetty be slotted?
Well, saw you additions and changes. It looks very good. Thanks for your work/support. Thought that nobody works/looks on it, because my version is about four month old... It is not necessary to slot the version. I'd slotted it because tomcat and other package are slotted, too. You could remove the slot, if you like to. Btw. is it possible that a jetty version >4 getting in to portage, soon?
Created attachment 58968 [details] jetty-5.1.3.ebuild Version bump. * Changed to SLOT="0" * Changed to ACCEPT_KEYWORDS="~x86" * Removed installation of a file that is no longer there The ${FILESDIR}/5.1.1 can be copied to ${FILESDIR}/5.1.3 Only the jetty.patch needs to be updated.
Created attachment 58970 [details, diff] jetty.patch for 5.1.3 One of the chunks from the jetty.patch for 5.1.1 failed, so this is a patch that applies cleanly.
Created attachment 62293 [details] jetty-5.1.3.ebuild Now all packed jars (for non-extras) are replaced with out own. Changed SLOT back to 5... not sure why I changed it at first. Fixed DEPEND and RDEPEND quite a bit: They were reversed, and DEPEND had RDEPEND in it.. Ant, jikes, junit, and unzip are now in DEPEND Libraries are now in JDEPEND jdk and jre are now in the DEPEND and RDEPEND respectively The extras have about 9 jars that still need to be replaced, so I disabled USE=extra, and all that that entails. I would imagine that the filesystem layout may need a bit of work. I would say it'd be best to try to mimic tomcat's where possible.
Well looks nice... Looking at it, the extra jars are indeed, too much. In my opinion a good solution is to split out the package into base (which is the current ebuild) and extra (which includes the extra file). Furthermore a meta ebuild "jetty" would be nice to install both. One question: is there a reason why you choose a hard fixed slot instead of a generic one ("${PV/.*}")?
Created attachment 62304 [details] jetty-5.1.3.ebuild This time I got it right I swear... * Finished commenteting out stuff from USE=extra :-[ * Reduced calls to ant down to one * Added javadoc creation / installation
Thanks for everyone's efforts on getting this ebuild to work. I ran into several instances where the ebuild and its associated files refered to "jetty5" while the actual reference should be "jetty-5". For example, $JETTY_USER is set as "jetty5" when, in reality, the user created during the emrge is "jetty-5"
*** Bug 94452 has been marked as a duplicate of this bug. ***
Made some typos corrections and depend/rdepend enlightments to make it work.
Closing bug. Removed from tree, till we get a maintainer and current version from source.
