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

Michael Koch konqueror at gmx.de
Mon Jan 7 08:03:36 UTC 2008


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





More information about the pkg-java-maintainers mailing list