On Sun, 09 Jan 2011 16:53:14 +0200
Ruslans Tarasovs <ruslan@xxxxxxxxx> wrote:
> Hi.
>
> I have tried to use the files you uploaded, but these still have
> exactly the same problem as described below. There is no main class
> description embedded into metainf file.
>
> I also tried to replace take that "start.jar" file from the latest
> non-debian distribution, but I got the error message that says that *
> is an invalid OPTIONS parameter.
>
> Another thing I tried is to build DEB files from the source, but
> there are some hardcoded paths (like /home/jesse). I did try to
> replace them, but there are seems to be more dependencies, so I did
> not have a successful build yet.
>
> Do you need anything else to know? I would be happy to help :)
>
> Best regards,
> Ruslans.
> > I have uploaded the 7.2.1.v20101111 debian files..
> >
> > let me know if you have any issues with them and we'll try and get
> > them sorted out
> >
> >
http://dist.codehaus.org/jetty/deb/
> >
> > cheers,
> > jesse
> >
> > --
> > jesse mcconnell
> > jesse.mcconnell@xxxxxxxxx
> >
> >
> >
> > On Thu, Nov 4, 2010 at 05:39, Jesse
> > McConnell<jesse.mcconnell@xxxxxxxxx> wrote:
> > > that is correct,
> > >
> > > the deb build is ultimately targeted to be picked up and used by
> > > deb distributions and those distributions won't pickup artifacts
> > > from a repo like that...they have to be built....and since they
> > > don't build with maven the debs are produced by a patched ant
> > > build.
> > >
> > > cheers,
> > > jesse
> > >
> > > --
> > > jesse mcconnell
> > > jesse.mcconnell@xxxxxxxxx
> > >
> > >
> > >
> > > On Thu, Nov 4, 2010 at 05:33, AS Maps<as.maps@xxxxxxxxx> wrote:
> > >> So the deb packaging does not seem to make use of the Maven
> > artifacts.
> > >>
> > >> MANIFEST.MF of
> > >> org.eclipse.jetty:jetty-start:jar:7.2.0.v20101020
> > consists of
> > >> the following lines
> > >>
> > >> Manifest-Version: 1.0
> > >> Archiver-Version: Plexus Archiver
> > >> Created-By: Apache Maven
> > >> Built-By: jesse
> > >> Build-Jdk: 1.6.0_19
> > >> Main-Class: org.eclipse.jetty.start.Main
> > >> Implementation-Vendor: Eclipse.org - Jetty
> > >> Implementation-Version: 7.2.0.v20101020
> > >> url:
http://www.eclipse.org/jetty
> > >>
> > >> Everything is fine with this manifest. What made me come to
> > >> this
> > idea was
> > >> the modification date of jetty-start.jar inside the deb
> > >> archive.
> > It is
> > >> 2010-10-27, creation date is 2010-11-04.
> > >>
> > >> I don't know how the deb build is done exactly, but to my
> > >> opinion
> > it doesn't
> > >> use any maven-ly produced artifacts.
> > >>
> > >> BTW: Have a good trip.
> > >>
> > >> Andreas
> > >>
> > >> On Thu, Nov 4, 2010 at 11:22 AM, Jesse
> > McConnell<jesse.mcconnell@xxxxxxxxx>
> > >> wrote:
> > >>>
> > >>>
> > >>>
> >
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
> > >>> jesse.mcconnell@xxxxxxxxx
> > >>>
> > >>>
> > >>>
> > >>> On Thu, Nov 4, 2010 at 05:17, AS Maps<as.maps@xxxxxxxxx>
> > >>> 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
> > >>> > <jesse.mcconnell@xxxxxxxxx>
> > >>> > 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
> > >>> >> jesse.mcconnell@xxxxxxxxx
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >> On Wed, Nov 3, 2010 at 11:38, Don
> > >>> >> Santillan<donzymeth@xxxxxxxxx> 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<donzymeth@xxxxxxxxx>
> > >>> >> > 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 tohttp://localhost:8080 <
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
> > >>> >> >> jetty-users@xxxxxxxxxxx
> > >>> >> >>
https://dev.eclipse.org/mailman/listinfo/jetty-users
> > >>> >> >>
> > >>> >> >
> > >>> >> > ________________________________
> > >>> >> > _______________________________________________
> > >>> >> > jetty-users mailing list
> > >>> >> > jetty-users@xxxxxxxxxxx
> > >>> >> >
https://dev.eclipse.org/mailman/listinfo/jetty-users
> > >>> >> >
> > >>> >> >
> > >>> >> > _______________________________________________
> > >>> >> > jetty-users mailing list
> > >>> >> > jetty-users@xxxxxxxxxxx
> > >>> >> >
https://dev.eclipse.org/mailman/listinfo/jetty-users
> > >>> >> >
> > >>> >> >
> > >>> >> _______________________________________________
> > >>> >> jetty-users mailing list
> > >>> >> jetty-users@xxxxxxxxxxx
> > >>> >>
https://dev.eclipse.org/mailman/listinfo/jetty-users
> > >>> >
> > >>> >
> > >>> > _______________________________________________
> > >>> > jetty-users mailing list
> > >>> > jetty-users@xxxxxxxxxxx
> > >>> >
https://dev.eclipse.org/mailman/listinfo/jetty-users
> > >>> >
> > >>> >
> > >>> _______________________________________________
> > >>> jetty-users mailing list
> > >>> jetty-users@xxxxxxxxxxx
> > >>>
https://dev.eclipse.org/mailman/listinfo/jetty-users
> > >>
> > >>
> > >> _______________________________________________
> > >> jetty-users mailing list
> > >> jetty-users@xxxxxxxxxxx
> > >>
https://dev.eclipse.org/mailman/listinfo/jetty-users
> > >>
> > >>
> > >
>
