http://repo2.maven.org/maven2/org/eclipse/jetty/jetty-distribution/7.2.0.v20101020/
you can have up a couple of dirs and go down the jetty-start path for a new start.jar (just rename it) past that, looks like I'll have to dig into it later (traveling atm) jesse -- jesse mcconnell [email protected] On Thu, Nov 4, 2010 at 05:17, AS Maps <[email protected]> wrote: > Hey Jesse, > > thanks for uploading. > > Unfortunately this is the content of jetty-start.jar\META-INF\MANIFEST.MF > > Manifest-Version: 1.0 > Ant-Version: Apache Ant 1.8.1 > Created-By: 1.6.0_0-b11 (Sun Microsystems Inc.) > > Where to check the artifacts in Maven repo (if any)? > > Regards > Andreas > > On Thu, Nov 4, 2010 at 11:02 AM, Jesse McConnell <[email protected]> > wrote: >> >> I have uploaded a hopefully uncorrupted file so hopefully that will >> address one of those issues...and ideally both. >> >> If the missing main class line in the start.jar is still a problem >> then I'll have to dig into the deb generation process and see what >> might have gone wrong, the 7.2.0 distribution itself is just fine. >> >> let me know if you still have issues after trying to newly uploaded jars >> >> md5 sums are: >> >> 1c700bdb09ac370472435631b9b85679 jetty_7.2.0.v20101020_all.deb >> 3238348f24cb7534cb112ae1144edb31 libjetty-java_7.2.0.v20101020_all.deb >> 9e984ab0954fefedfe80b26f08a18f27 >> libjetty-java-doc_7.2.0.v20101020_all.deb >> >> jesse >> -- >> jesse mcconnell >> [email protected] >> >> >> >> On Wed, Nov 3, 2010 at 11:38, Don Santillan <[email protected]> wrote: >> > This is different in my case. I have 40kb for the start.jar and looking >> > in >> > the manifest file for it, I found that it is missing its main-class >> > property. >> > >> > Manifest-Version: 1.0 >> > Ant-Version: Apache Ant 1.8.1 >> > Created-By: 1.6.0_0-b11 (Sun Microsystems Inc.) >> > >> > So what I did was to add the main-class into the manifest file, such as >> > this: >> > >> > Manifest-Version: 1.0 >> > Ant-Version: Apache Ant 1.8.1 >> > Main-Class: org.eclipse.jetty.start.Main >> > Created-By: 1.6.0_0-b11 (Sun Microsystems Inc.) >> > >> > This time, the command found the main class but still produced an error: >> > >> > prompt$ /usr/bin/java -DSTART=/usr/share/jetty/etc/start.config -Xmx256m >> > -Djava.awt.headless=true >> > -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >> > -Djetty.port=8080 -Djetty.home=/usr/share/jetty -Djava.io.tmpdir=/tmp >> > -jar >> > /usr/share/jetty/start.jar --pre=etc/jetty-logging.xml >> > java.lang.IllegalArgumentException: No such OPTIONS: Server >> > at >> > org.eclipse.jetty.start.Config.getCombinedClasspath(Config.java:400) >> > at >> > org.eclipse.jetty.start.Config.getActiveClasspath(Config.java:377) >> > at org.eclipse.jetty.start.Main.start(Main.java:536) >> > at org.eclipse.jetty.start.Main.parseCommandLine(Main.java:280) >> > at org.eclipse.jetty.start.Main.main(Main.java:82) >> > Use java -jar start.jar --help for usage information. >> > prompt$ >> > >> > -don >> > >> > AS Maps wrote: >> > >> > I examined the jar inside of the deb file libjetty-java_*_all.deb and it >> > turned out that its size is 0 bytes. >> > So there is rarely any file inside this obviously corrupted file. >> > >> > Maybe a new build must be done. >> > >> > On Wed, Nov 3, 2010 at 4:33 PM, Don Santillan <[email protected]> >> > wrote: >> >> >> >> Hello, >> >> >> >> I'm having problems starting jetty 7.2.0.v20101020 right after >> >> installation. Here's what I did so far. >> >> >> >> 1. Download the following deb files: >> >> a. wget >> >> >> >> http://dist.codehaus.org/jetty/deb/7.2.0.v20101020/jetty_7.2.0.v20101020_all.deb >> >> b. wget >> >> >> >> http://dist.codehaus.org/jetty/deb/7.2.0.v20101020/libjetty-java-doc_7.2.0.v20101020_all.deb >> >> c. wget >> >> >> >> http://dist.codehaus.org/jetty/deb/7.2.0.v20101020/libjetty-java_7.2.0.v20101020_all.deb >> >> >> >> 2. Make downloaded deb files executable: >> >> a. chmod +x jetty_7.2.0.v20101020_all.deb >> >> b. chmod +x libjetty-java-doc_7.2.0.v20101020_all.deb >> >> c. chmod +x libjetty-java_7.2.0.v20101020_all.deb >> >> >> >> 3. Installed the deb files in the following order: >> >> a. sudo dpkg -i libjetty-java-doc_7.2.0.v20101020_all.deb >> >> (Reading database ... 328484 files and directories currently >> >> installed.) >> >> Preparing to replace libjetty-java-doc 6.1.20-2 (using >> >> libjetty-java-doc_7.2.0.v20101020_all.deb) ... >> >> Unpacking replacement libjetty-java-doc ... >> >> Setting up libjetty-java-doc (7.2.0.v20101020) ... >> >> Processing triggers for doc-base ... >> >> Processing 1 removed doc-base file(s)... >> >> Registering documents with scrollkeeper... >> >> >> >> b. sudo dpkg -i libjetty-java_7.2.0.v20101020_all.deb >> >> (Reading database ... 328672 files and directories currently >> >> installed.) >> >> Preparing to replace libjetty-java 6.1.20-2 (using >> >> libjetty-java_7.2.0.v20101020_all.deb) ... >> >> Unpacking replacement libjetty-java ... >> >> Setting up libjetty-java (7.2.0.v20101020) ... >> >> >> >> c. sudo dpkg -i jetty_7.2.0.v20101020_all.deb >> >> (Reading database ... 328763 files and directories currently >> >> installed.) >> >> Preparing to replace jetty 7.2.0.v20101020 (using >> >> jetty_7.2.0.v20101020_all.deb) ... >> >> Unpacking replacement jetty ... >> >> Setting up jetty (7.2.0.v20101020) ... >> >> Adding system user `jetty' (UID 117) ... >> >> Adding new group `jetty' (GID 127) ... >> >> Adding new user `jetty' (UID 117) with group `jetty' ... >> >> Not creating home directory `/usr/share/jetty'. >> >> update-rc.d: warning: /etc/init.d/jetty missing LSB information >> >> update-rc.d: see <http://wiki.debian.org/LSBInitScripts> >> >> Starting Jetty: Not starting jetty - NO_START=1 >> >> >> >> Processing triggers for ureadahead ... >> >> >> >> 4. Change the following in /etc/default/jetty: >> >> a. NO_START=1 to NO_START=0 >> >> b. UNcommented JETTY.PORT=8080 >> >> c. set JAVA_HOME=/usr/lib/jvm/java-6-sun >> >> 5. Run jetty: >> >> a. sudo /etc/init.d/jetty start >> >> >> >> 6. Here's what I got: >> >> Starting Jetty: FAILED >> >> >> >> 7. Run "sudo /etc/init.d/jetty check" and here's what I got: >> >> Checking arguments to Jetty: >> >> JETTY_HOME = /usr/share/jetty >> >> JETTY_CONF = /usr/share/jetty/etc/jetty.conf >> >> JETTY_RUN = /var/run >> >> JETTY_PID = /var/run/jetty.pid >> >> JETTY_PORT = 8080 >> >> JETTY_LOGS = >> >> START_INI = >> >> CONFIGS = --pre=etc/jetty-logging.xml >> >> JAVA_OPTIONS = -DSTART=/usr/share/jetty/etc/start.config -Xmx256m >> >> -Djava.awt.headless=true >> >> -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >> >> -Djetty.port=8080 -Djetty.home=/usr/share/jetty -Djava.io.tmpdir=/tmp >> >> JAVA = /usr/bin/java >> >> CLASSPATH = >> >> RUN_CMD = /usr/bin/java >> >> -DSTART=/usr/share/jetty/etc/start.config >> >> -Xmx256m -Djava.awt.headless=true >> >> -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >> >> -Djetty.port=8080 -Djetty.home=/usr/share/jetty -Djava.io.tmpdir=/tmp >> >> -jar >> >> /usr/share/jetty/start.jar --pre=etc/jetty-logging.xml >> >> >> >> Jetty running pid=24388 >> >> >> >> * Notice the running pid=24388 line. This means the pid was created. >> >> But >> >> going to http://localhost:8080 shows the service is offline. >> >> >> >> 8. Run the following command on a separate terminal: >> >> /usr/bin/java -DSTART=/usr/share/jetty/etc/start.config -Xmx256m >> >> -Djava.awt.headless=true >> >> -Dorg.eclipse.jetty.util.log.class=org.eclipse.jetty.util.log.StdErrLog >> >> -Djetty.port=8080 -Djetty.home=/usr/share/jetty -Djava.io.tmpdir=/tmp >> >> -jar >> >> /usr/share/jetty/start.jar --pre=etc/jetty-logging.xml >> >> >> >> Shows the following: >> >> Failed to load Main-Class manifest attribute from >> >> /usr/share/jetty/start.jar >> >> >> >> 9. Here's my jetty home directory listing at /usr/share/jetty: >> >> total 28 >> >> drwxr-xr-x 4 root root 4096 2010-11-03 23:30 . >> >> drwxr-xr-x 353 root root 12288 2010-10-27 13:41 .. >> >> lrwxrwxrwx 1 root root 19 2010-11-03 22:58 contexts -> >> >> /etc/jetty/contexts >> >> lrwxrwxrwx 1 root root 10 2010-11-03 22:58 etc -> /etc/jetty >> >> lrwxrwxrwx 1 root root 24 2010-11-03 22:59 javadoc -> >> >> ../doc/libjetty-java/api >> >> drwxr-xr-x 5 root root 4096 2010-11-03 22:59 lib >> >> lrwxrwxrwx 1 root root 14 2010-11-03 22:58 logs -> /var/log/jetty >> >> drwxr-xr-x 2 root root 4096 2010-11-03 22:59 resources >> >> -rw-rw-r-- 1 root root 2010 2010-11-03 23:30 start.ini >> >> lrwxrwxrwx 1 root root 39 2010-11-03 22:59 start.jar -> >> >> ../java/jetty-start-7.2.0.v20101020.jar >> >> lrwxrwxrwx 1 root root 22 2010-11-03 22:58 webapps -> >> >> /var/lib/jetty/webapps >> >> >> >> Is there a problem with the manifest file of >> >> /usr/share/jetty/start.jar? >> >> What seems to be the problem? >> >> >> >> -don >> >> >> >> _______________________________________________ >> >> jetty-users mailing list >> >> [email protected] >> >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> >> >> > >> > ________________________________ >> > _______________________________________________ >> > jetty-users mailing list >> > [email protected] >> > https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >> > >> > _______________________________________________ >> > jetty-users mailing list >> > [email protected] >> > https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >> > >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/jetty-users > > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > > _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
