Please find attached a new ebuild for Jetty 6.1.24. It is required for Eclipse 3.5.2.
Created attachment 239169 [details] jetty-6.1.24.ebuild
This ebuild currently isn't good enough to be merged into the tree. Within java-experimental there seems to be a set of packages that could be a good starting point for an attempt. We will need to figure out whether we can package the jetty servlet/jsp api in a way that will work with java-virtuals/servlet-api. Sadly it seems that until this is done eclipse will not be updated.
Created attachment 252235 [details] my try at a new ebuild
Created attachment 252237 [details] files/pom.xml
Created attachment 252239 [details] files/pom-terracotta.xml
Created attachment 252241 [details] files/settings.xml
Created attachment 252243 [details] jetty-1.6.24.ebuild
Created attachment 252247 [details] jetty-6.1.24.ebuild sorry, I was a little too quick to add the last one. I changed the way I choose what jars to install. I'll be testing that I can get an actual instance of jetty running sometime later, but at least this gives people something to kick around.
Created attachment 252305 [details] files/init.d/jetty
Created attachment 252307 [details] files/conf.d/jetty
Created attachment 252309 [details] jetty-6.1.24.ebuild Adds in more install libs and fixes the setuid dependency. Also adds in a basic init script, although I'm having some issues getting jetty to start. my guess is I'm missing a required property somewhere
Created attachment 252543 [details] jetty-6.1.24.ebuild removes need for special pom files as it now uses sed to strip out what we don't wan to build.
Created attachment 252545 [details] files/conf.d/jetty updated conf.d file
Created attachment 252547 [details] files/init.d/jetty updated init.d file. jetty now starts properly
John's ebuild works well; I was able to use it to build Eclipse 3.6 from the ebuild in Bug #325271. It did hiccup, however, after installing Maven: it tried to call `mvn` but neither installed version of Maven on my system had installed that binary. A simple `eselect maven set mvn-2.2` solved that problem.
Very nice ebuild. Does the ebuild work offline? It allways tries to download jetty-parent-9.pom Cheers :-)
after manually generating a symbolic link for maven mvn in /usr/bin the ebuild proceeded until the following URL could not be found: Project ID: org.terracotta.maven.plugins:tc-maven-plugin Reason: POM 'org.terracotta.maven.plugins:tc-maven-plugin' not found in repository: Unable to download the artifact from any repository org.terracotta.maven.plugins:tc-maven-plugin:pom:1.1.8
(In reply to comment #16) > Very nice ebuild. > > Does the ebuild work offline? sorry, forgot to add myself to the CC then promptly forgot about the bug. As far as I know it will not work in offline mode since maven always wants to try and update from it's own repositories. I think the only way to get this to work in full offline mode will be to bypass maven and create an ebuild for each dependency. At the moment, that's more work than I want to put into this since the only thing I use Jetty for is to compile Eclipse. the other option is to create an ebuild off of bug #175054 as I think that may support offline builds
(In reply to comment #17) > after manually generating a symbolic link for maven mvn in /usr/bin the ebuild > proceeded until the following URL could not be found: > > Project ID: org.terracotta.maven.plugins:tc-maven-plugin > > Reason: POM 'org.terracotta.maven.plugins:tc-maven-plugin' not found in > repository: Unable to download the artifact from any repository > > org.terracotta.maven.plugins:tc-maven-plugin:pom:1.1.8 (In reply to comment #15) > A simple `eselect maven set mvn-2.2` solved that problem. That should be all you have to do. Creating manual links is bad form in Gentoo. you should always see if there is an eselect for a package before resorting to that.
Well, i get [ERROR] Error executing Maven. when trying to use maven-bin-3.0.2 and ACCESS DENIED mkdir /root/.m2/repository/org/foo when using maven 2.2.1.
I cannot build it with maven 3: [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.mortbay.jetty:jetty-setuid:6.1.24 (/home/repositories/tmp/portage/www-servers/jetty-6.1.24/work/jetty-6.1.24/extras/setuid/pom.xml) has 1 error [ERROR] 'profiles.profile.id' must be unique but found duplicate profile with id env-windows @ line 147, column 17 [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
Jetty 6 is not compatable with Maven 3. It needs to be compiled with maven 2.
I don't understand what prevents this ebuild from hiting the main tree: As far as I can see, it only lacks a definition to require maven 2 instead of 3, isn't it? I'm not a package maintainer or have any idea where to start this, but since this is blocking two bugs so far, isn't it time to get this running?
(In reply to comment #23) > I don't understand what prevents this ebuild from hiting the main tree: As far > as I can see, it only lacks a definition to require maven 2 instead of 3, isn't > it? > > I'm not a package maintainer or have any idea where to start this, but since > this is blocking two bugs so far, isn't it time to get this running? > Both bugs affect the same package (eclipse) and the solution I made requiring maven is mostly a hack. The provided overlay for eclipse is a suitable workaround at this time.
(In reply to comment #24) > Both bugs affect the same package (eclipse) and the solution I made requiring > maven is mostly a hack. The provided overlay for eclipse is a suitable > workaround at this time. I totally appreciate your provided workaround with the overlay! But that's what I'm not understanding: As far as I know, is an overlay simply an additional source for portage atoms, isn't it? What makes these packages not hiting the main tree currently?
> I'm not understanding: > As far as I know, is an overlay simply an additional source for portage atoms, > isn't it? yes it is an additional repository. > What makes these packages not hiting the main tree currently? Mostly because the ebuilds contained within this bug report are not of a high enough quality. e.g. They use maven to build which we currently don't support. If you read all the comments you will be able to get the idea.
(In reply to comment #17) > after manually generating a symbolic link for maven mvn in /usr/bin the ebuild > proceeded until the following URL could not be found: > > Project ID: org.terracotta.maven.plugins:tc-maven-plugin > > Reason: POM 'org.terracotta.maven.plugins:tc-maven-plugin' not found in > repository: Unable to download the artifact from any repository > > org.terracotta.maven.plugins:tc-maven-plugin:pom:1.1.8 Have you work it out? I have the same error but "eselect maven set mvn-2.2" didn't helped.
*** Bug 367541 has been marked as a duplicate of this bug. ***
Created attachment 274803 [details] virtual/jetty-6.ebuild Here is a virtual package for managing jetty installs
Created attachment 274807 [details] www-servers/jetty-bin-6.1.26.ebuild This ebuild still requires the same init.d and conf.d files
Created attachment 274827 [details] www-servers/jetty-bin-6.1.26.ebuild fixes the location of package.env
Created attachment 274835 [details] java-virtuals/jetty-server/jetty-server-6.ebuild changes to use the java-virtuals
Created attachment 274849 [details] www-servers/jetty-bin-6.1.26.ebuild fixed now that the virtual package is properly using the java-virtuals
Just a question: Why did you comment out all actions to merge jetty-bin as "jetty"? The product itself is not named "jetty-bin", right? My problem is, that the eclipse-3.7 ebuilds from Bug 325271 do not merge with jetty being installed as "jetty-bin-6", eclipse expects a product called "jetty-6" to be installed. After changing the ebuild to merge as "jetty", eclipse merges fine. But it has to be noted that I did not have the time to test eclipse-3.7 properly, yet! However, until I have tested everything properly I have added your jetty-bin-6.1.26.ebuild and virtual jetty-server-6.ebuild to my gentoo overlay (layman -a seden) for further testing. The ChangeLog states that you are the rightful author of the ebuilds, I hope that is ok with you?
Created attachment 283873 [details] jetty-bin-6.1.26-r1.ebuild Changed to install as "jetty" instead of "jetty-bin".
"This ebuild currently isn't good enough to be merged into the tree." --> What's missing/not working?
Alistair (or other devs), could we get some feedback on the jetty-bin ebuild please? It doesn't require maven to build, so it would be great to see it hit the main portage tree. Thanks.
Just a question: What about Jetty-7 or 8? The Eclipse download page (http://download.eclipse.org/jetty/) does not speak of version 6, and this very version 6 makes it impossible to view the contents of the help center.
(In reply to comment #26) > Mostly because the ebuilds contained within this bug report are not of a > high enough quality. e.g. They use maven to build which we currently don't > support. > > If you read all the comments you will be able to get the idea. It does not depend on users writing ebuilds whether a software hits the tree. +1 vote for the java team to take over this issue
(In reply to comment #38) > Just a question: What about Jetty-7 or 8? The Eclipse download page > (http://download.eclipse.org/jetty/) does not speak of version 6, and this > very version 6 makes it impossible to view the contents of the help center. Sven, I think this would be the best route to take with the Jetty dependencies. Version 7 is probably minimal at this point, but bumping to 8 is worth a try to see is eclipse can work with it. I know when I use the eclipse-bin install with the packaged maven, maven is pulling jetty 8 binaries (maven goal jetty:run).
Comment on attachment 274849 [details] www-servers/jetty-bin-6.1.26.ebuild obsoleted by Svens overlay (seden)
(In reply to comment #40) > (In reply to comment #38) > > Just a question: What about Jetty-7 or 8? The Eclipse download page > > (http://download.eclipse.org/jetty/) does not speak of version 6, and this > > very version 6 makes it impossible to view the contents of the help center. > Just tried updating the ebuilds to compile against jetty7, and it looks like eclipse is still expecting jetty6 which has a package space of org.mortbay while jetty7+ has a package space of org.eclipse
(In reply to comment #42) > Just tried updating the ebuilds to compile against jetty7, and it looks like > eclipse is still expecting jetty6 which has a package space of org.mortbay > while jetty7+ has a package space of org.eclipse I was actually successful in compiling Juno against Jetty 8 but lost the ebuild because of a hard disk crash. AFAIR, a plugin which requires Jetty 6 complains about the package not being present but eclipse still builds without it. The plugin is probably pending removal. And neither does dependencies.properties list that package.
Created attachment 321512 [details] jetty-7.6.5.v20120716.ebuild Jetty 7 ebuild that installs nicely, but I think that the start.config controls at the end have to be updated a little more. I couldn't actually get an instance of jetty running.
Created attachment 321514 [details] init.d/jetty-7 updated init.d for jetty 7
Hi. It seems this bug has stalled. Unfortunately this is blocking the online banking application hibiscus. Looking at the comments, it’s unclear what’s required to close this. I’m interested in helping wherever I can, to get this working. I only need to know what needs to be done.
There's a webapp we're going to be deploying soon that requires either jetty 9 (latest) or 8 (still maintained upstream), it would sure be nice if there were an official ebuild for it. Any updates or status on this? Is the delay a lack of dev interest or time or? Thanks...
(In reply to Paul B. Henson from comment #47) > Any updates or status on this? Is the delay a lack of dev interest or time or? It's one of the hardest Java packages of all to package and we're already overworked dealing with what we have. Sorry.
