Bug#458399: jetty: Jetty depends on a java 1.5 package

2008-01-07 Thread Michael Koch
On Wed, Jan 02, 2008 at 11:39:05PM +0100, Marcel Ammerlaan wrote:
 On Mon, Dec 31, 2007 at 12:15:13AM +0100, marcel wrote:
  Package: jetty
  Version: 5.1.14-1
  Severity: important
 
  The JspServlet contained in libtomcat5.5-java is compiled with Java 1.5 
  (class version 49.0)
  which will not run on a java 1.4 runtime which should be enough to run 
  Jetty.
  
 
  The problem is that Jetty depends on (and uses) libtomcat5.5-java. The
  Tomcat source uses (among other Java5 features) generics. That is the
  reason wht this class file is only for Java5 and the reason why jetty in
  Debian needs Java5 too.
 

 This differs from the download package of Jetty which runs on older 
 versions of Java as well.
 I see two options:
 1) Make it clear that a java2-runtime is not enough
 2) Decouple jetty from tomcat and distribute the complete jetty package 
 instead.
 (maybe even conflict with tomcat? Why would you want two servlet engines 
 on the same machine?)

Unfortunately we have currently no way to tell a package that is needs
Java5 or newer stuff. You are right in saying that Debian now mainly
supports Java5/6 on all platforms. arm is a special case here as our
main runtime (GCJ) doesnt really work there due to several problems.

What about using jamvm or cacao? These support java 5 stuff too and
unline GCJ they work on arm.

 Of course, the last alternative is to keep it as as, as only java1.5/1.6 
 and gcj are officially in Debian
 anyway. If this is the case, please feel free to close this report.

I tend to keep this bug open but tag it 'wontfix'. I will need to think
some days about this.


Cheers,
Michael



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#458399: jetty: Jetty depends on a java 1.5 package

2008-01-07 Thread Michael Koch
On Mon, Jan 07, 2008 at 09:36:45AM +1100, Greg Wilkins wrote:
 
 While Jetty can run on a 1.4 JVM, perhaps in debian it may just be
 simpler to build it only run with 1.5 and later.

The bug reporter is a very special situation as we wants to run jetty on
an arm architecture which is not supported by SUN nor by GCJ.

 After all, java was only really open sourced from 1.5.

Java is really open sourced from 7. Java 5 and 6 are still closed source
and probably ever will be.


Cheers,
Michael



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#458399: jetty: Jetty depends on a java 1.5 package

2008-01-06 Thread Greg Wilkins

While Jetty can run on a 1.4 JVM, perhaps in debian it may just be
simpler to build it only run with 1.5 and later.

After all, java was only really open sourced from 1.5.

cheers




___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#458399: jetty: Jetty depends on a java 1.5 package

2008-01-02 Thread Marcel Ammerlaan
On Mon, Dec 31, 2007 at 12:15:13AM +0100, marcel wrote:
 Package: jetty
 Version: 5.1.14-1
 Severity: important

 The JspServlet contained in libtomcat5.5-java is compiled with Java 1.5 
 (class version 49.0)
 which will not run on a java 1.4 runtime which should be enough to run Jetty.
 

 The problem is that Jetty depends on (and uses) libtomcat5.5-java. The
 Tomcat source uses (among other Java5 features) generics. That is the
 reason wht this class file is only for Java5 and the reason why jetty in
 Debian needs Java5 too.

   
This differs from the download package of Jetty which runs on older 
versions of Java as well.
I see two options:
1) Make it clear that a java2-runtime is not enough
2) Decouple jetty from tomcat and distribute the complete jetty package 
instead.
(maybe even conflict with tomcat? Why would you want two servlet engines 
on the same machine?)

Of course, the last alternative is to keep it as as, as only java1.5/1.6 
and gcj are officially in Debian
anyway. If this is the case, please feel free to close this report.

Regards,

Marcel Ammerlaan.





___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#458399: jetty: Jetty depends on a java 1.5 package

2007-12-30 Thread marcel
Package: jetty
Version: 5.1.14-1
Severity: important

The JspServlet contained in libtomcat5.5-java is compiled with Java 1.5 (class 
version 49.0)
which will not run on a java 1.4 runtime which should be enough to run Jetty.
The error in the jetty out.log is:

java.lang.reflect.InvocationTargetException
at java.lang.reflect.Method.invoke(Unknown Source)
at org.mortbay.start.Main.invokeMain(Unknown Source)
at org.mortbay.start.Main.start(Unknown Source)
at org.mortbay.start.Main.main(Unknown Source)
Caused by: java.lang.UnsupportedClassVersionError: 
org/apache/jasper/servlet/JspServlet (Unsupported major.minor version 49.0)
  at java.lang.ClassLoader.defineClass0(Native Method)
  at java.lang.ClassLoader.defineClass(Compiled Method)(Unknown Source)
  at java.security.SecureClassLoader.defineClass(Unknown Source)
  at java.net.URLClassLoader.defineClass(Unknown Source)
  at java.net.URLClassLoader$1.run(Unknown Source)
  at java.security.AccessController.doPrivileged(Unknown Source)
  at java.net.URLClassLoader.findClass(Unknown Source)
  at java.lang.ClassLoader.loadClass(Unknown Source)
  at java.lang.ClassLoader.loadClass(Unknown Source)
  at org.mortbay.http.ContextLoader.loadClass(Unknown Source)
  at org.mortbay.http.ContextLoader.loadClass(Unknown Source)
  at org.mortbay.http.HttpContext.loadClass(Unknown Source)
  at org.mortbay.jetty.servlet.Holder.start(Unknown Source)
  at org.mortbay.jetty.servlet.ServletHolder.start(Unknown Source)
  at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(Unknown Source)
  at org.mortbay.jetty.servlet.WebApplicationHandler.initializeServlets(Unknown 
Source)
  at org.mortbay.jetty.servlet.WebApplicationContext.doStart(Unknown Source)
  at org.mortbay.util.Container.start(Unknown Source)
  at org.mortbay.http.HttpServer.doStart(Unknown Source)
  at org.mortbay.util.Container.start(Unknown Source)
  at org.mortbay.jetty.Server.main(Unknown Source)
  ... 4 more


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: arm (armv5tel)

Kernel: Linux 2.6.22-3-ixp4xx
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages jetty depends on:
ii  adduser   3.105  add and remove users and groups
ii  ant   1.7.0-3Java based build tool like make
ii  apache2-utils 2.2.6-3utility programs for webservers
ii  java2-equivs [java2-runtime]  1.0Equivs package for Sun JDK1.4/Arm/
ii  libcommons-logging-java   1.1.1-1commmon wrapper interface for seve
ii  libmx4j-java  3.0.1-3An open source implementation of t
ii  libservlet2.4-java5.0.30-6   Servlet 2.4 and JSP 2.0 Java class
ii  libtomcat5.5-java 5.5.25-3   Java Servlet engine -- core librar
ii  libxerces2-java   2.9.0-1Validating XML parser for Java wit

jetty recommends no packages.

-- no debconf information




___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers