Hi Torsten, libjetty-setuid-java contained both Java and native code, and this caused problems during the builds as highlighted by Thierry Carrez.
>From Thieery Carrez: > Build on i386 succeeded (as it is the one used in the "all" build) but > amd64 fails (missing servlet and slf4j classes...) > Ideally the package would be splitted in a way that Java code isn't > built as 'any' at all, only C code would ? I have reorganized the packaging to move most of libjetty-setuid-java to libjetty-extra-java, and put the native code into libjetty-extra. Since we decided to migrate jetty to the new jetty6 package, I did not worry too much about backwards compatibility... Ludovic Torsten Werner a écrit : > Hi Ludovic, > > On Mon, Sep 7, 2009 at 1:35 AM, Ludovic > Claude<[email protected]> wrote: >> I'm pushing back quickly in SVN the fixes I made for the jetty6 package >> into jetty, can you have a look at them and release them? > > why do we have a new binary package libjetty-extra package now? What > was wrong with libjetty-setuid-java? > > Cheers, > Torsten > > _______________________________________________ pkg-java-maintainers mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
