Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #12474

Re: OpenJDK for Bookworm and beyond

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tuesday, 8 November 2022 19:51:12 GMT Moritz Mühlenhoff wrote:
> Am Thu, Sep 29, 2022 at 02:06:06PM +0200 schrieb Thorsten Glaser:
> > > Last point, we still have OpenJDK 8 in unstable to help with the
> > > bootstrapping of some packages that can't build directly with the
> > > latest JDK (more specifically, Kotlin and Scala). Similarly I think we
> > > should preserve OpenJDK 11 in unstable after the transition to OpenJDK
> > > 17.
> > 
> > Who’s going to maintain that?
> > 
> > For OpenJDK 8 I took over because,
> 
> Do we even have to keep 8 around in unstable at this point? If people want
> to bootstrap kotlin or scala for a new arch, why can't this happen on a
> buster system?
> 
> Cheers,
>         Moritz
Every current version of Scala runs on OpenJDK 11 or above.  See:-


https://docs.scala.org/overviews/jdk-compatibility/overview.html


The only code that really needs to be in Debian for building anything scala related is sbt 
(which needs a current 2.12 to build), and that is the only bit of the scala infrastructure 
that is up to date (at 1.7.3 which is the latest version).


The scala compiler and other libraries currently on Debian are so out of date as to be of no 
use.  Sbt downloads everything it and the project you are building including the compiler 
from Maven so having them in Debian is redundant.


The only sensible alternatives to sbt are mill (not currently in Debian) and gradle (which 
currently says it needs openjdk 8) which used for projects which are mixed java and scala.

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-09-29 12:10 +0200
  Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-09-29 14:10 +0200
    Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-09-29 20:10 +0200
      Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-09-29 20:40 +0200
      Re: OpenJDK for Bookworm and beyond Phil Morrell <debian@emorrp1.name> - 2022-10-12 02:00 +0200
    Re: OpenJDK for Bookworm and beyond Moritz Mühlenhoff <jmm@inutil.org> - 2022-11-08 21:00 +0100
      Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-08 21:00 +0100
      Re: OpenJDK for Bookworm and beyond David Goodenough <david.goodenough@linkchoose.co.uk> - 2022-11-09 12:50 +0100
  Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-10-31 19:50 +0100
    Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-10-31 20:00 +0100
      Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-10 21:40 +0100
        Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-10 22:20 +0100
          Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-10 22:50 +0100
            Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-11 01:40 +0100
              Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-11 01:50 +0100
                Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-11 12:00 +0100
                Re: OpenJDK for Bookworm and beyond Thorsten Glaser <t.glaser@tarent.de> - 2022-11-11 16:30 +0100
          Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-10 22:50 +0100
  Re: OpenJDK for Bookworm and beyond Moritz Mühlenhoff <jmm@inutil.org> - 2022-11-08 20:50 +0100
    Re: OpenJDK for Bookworm and beyond Emmanuel Bourg <ebourg@apache.org> - 2022-11-10 20:40 +0100

csiph-web