all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: Using openjdk9 as the default JDK
Date: Tue, 05 Mar 2019 10:35:07 +0100	[thread overview]
Message-ID: <b46a926a347cf7403175d8c52f8db020@lepiller.eu> (raw)
In-Reply-To: <874l8hwuwk.fsf@elephly.net>

Le 2019-03-05 10:08, Ricardo Wurmus a écrit :
> Hi Guix,
> 
> there are a few packages now that require Java 9, such as
> java-eclipse-jdt-compiler-apt (that I’m currently packaging).
> 
> We should aim to use openjdk9 as the default JDK.
> 
> What do you think?
> 
> --
> Ricardo

sounds good, but that will give us a lot of work.

I'd like to suggest upgrading to java 11 instead, and build
packages that don't support it with the -source argument.

I've got some packages locally that require -source 1.6 and
one that requires -source 1.4. I do it in this way currently:

(add-before 'build 'use-1.4
   (lambda _
     (substitute* "build.xml"
       (("<javac") "<javac source=\"1.4\""))))

The build.xml is generated from the ant-build-system, so maybe
we could add a #:source-version key to do just that? Doing it
this way prevents some warning (and sometimes errors) that
appear when using an older compiler on a package with dependencies
that were build with a newer compiler.

I think our update to the latest openjdk would be a lot smoother
with this. What do you think?

  reply	other threads:[~2019-03-05  9:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05  9:08 Using openjdk9 as the default JDK Ricardo Wurmus
2019-03-05  9:35 ` Julien Lepiller [this message]
2019-03-05  9:35 ` Gábor Boskovits
2019-03-05  9:46   ` Ricardo Wurmus
2019-03-05 19:00     ` Alex Vong
2019-03-05 20:32       ` Gábor Boskovits
2019-03-14 18:33         ` Alex Vong
2019-03-18  4:50         ` Chris Marusich
2019-03-06  7:12       ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b46a926a347cf7403175d8c52f8db020@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.