Le 05/02/2019 à 15:05, Emmanuel Bourg a écrit :
> The real issue is lombok, it needs both Java 8 and 11 to build (and even
> 6 and 7! But we managed do to without that).
Erratum: I've just figured out how to build lombok with Java 11 only.
Once ivyplusplus is taught about the new javac 'release'
Hi all,
Le 05/02/2019 à 14:24, Per Lundberg a écrit :
> is this the correct list of packages which can only be built w/ openjdk-8
That's almost correct:
- jzmq and openjfx are built with openjdk-11 already
- openjdk-8-jre-dcevm has just been removed, replaced by
openjdk-11-jre-dcevm (not in
On 2/4/19 10:07 PM, Moritz Mühlenhoff wrote:
> What is the specific use case for this, is there some package which
> needs 8 and can't be fixed in time for 11?
Yes, it was stated in this thread earlier that such packages do exist.
Emmanuel/others, is this the correct list of packages which can
On Mon, Feb 04, 2019 at 03:04:41PM +0100, Markus Koschany wrote:
> I would add a NEWS file to OpenJDK 8 and explain the situation and in
> addition create a wrapper around the OpenJDK 8 java command that prints
> out a message and quits. javac shall continue to work because it is
> needed to build
Am 04.02.19 um 14:56 schrieb Per Lundberg:
> On 2/1/19 11:20 AM, Matthias Klose wrote:
>> On 01.02.19 10:03, Emmanuel Bourg wrote:
>
>>> This is an excellent suggestion. We should file a bug for openjdk-8 to
>>> implement that.
>> please attach the patch.
>
> Sure, I should be able to write
On 2/1/19 11:20 AM, Matthias Klose wrote:
> On 01.02.19 10:03, Emmanuel Bourg wrote:
>> This is an excellent suggestion. We should file a bug for openjdk-8 to
>> implement that.
> please attach the patch.
Sure, I should be able to write something up. Forbear my ignorance:
should I use debconf
On 01.02.19 10:03, Emmanuel Bourg wrote:
> Le 01/02/2019 à 09:17, Per Lundberg a écrit :
>
>> I think that risk is significant. If we go that route, I would suggest a
>> postinst/debhelper message saying that "OpenJDK 8 is included but
>> unsupported. Many packages will not work with it. Use at
Le 01/02/2019 à 09:17, Per Lundberg a écrit :
> I think that risk is significant. If we go that route, I would suggest a
> postinst/debhelper message saying that "OpenJDK 8 is included but
> unsupported. Many packages will not work with it. Use at your own risk."
> or something similar.
This
On 1/29/19 3:36 PM, Markus Koschany wrote:
> We usually ship only with one JDK per release because of security
> support. OpenJDK 8 will be EOL before the end of the Debian 10 release
> cycle. We still have a couple of packages that will not compile with
> OpenJDK 11 hence we also thought about
Am 29.01.19 um 14:19 schrieb Per Lundberg:
> Hi Markus,
>
> On 1/29/19 1:32 PM, Markus Koschany wrote:
>>
>>> I am sorry but OpenJDK 8 will not be supported at runtime in
>>> Buster.
> Another question: if this is the case, should the openjdk-8-jdk package
> (and friends) be removed altogether
Le 29/01/2019 à 14:19, Per Lundberg a écrit :
> Another question: if this is the case, should the openjdk-8-jdk package
> (and friends) be removed altogether in sid?
We can't remove openjdk-8 yet, it's still required to build some
convoluted packages. But Buster will only support OpenJDK 11,
Am 29.01.19 um 13:54 schrieb Per Lundberg:
[...]
> But, the approach you suggest is fine. Markus, will you reopen this bug
> or should we file a new one about it, what do you prefer?
I think we don't need a new bug report for that. I will change that
later today.
Regards,
Markus
Hi Markus,
On 1/29/19 1:32 PM, Markus Koschany wrote:
>
>> I am sorry but OpenJDK 8 will not be supported at runtime in
>> Buster.
Another question: if this is the case, should the openjdk-8-jdk package
(and friends) be removed altogether in sid? I looked briefly but
couldn't find any bugs
On 1/29/19 1:32 PM, Markus Koschany wrote:
Hi Markus and Emmanuel,
Emmanuel - the problem is that VisualVM will display its splash screen,
then die with an error in the log about java.lang.NoSuchMethodError:
java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;
>> I am sorry but OpenJDK 8 will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 29.01.19 um 12:06 schrieb Markus Koschany:
> I am sorry but OpenJDK 8 will not be supported at runtime in
> Buster. If it works with OpenJDK 11, which it does, then we should
> spend the remaining time before the release on more urgent issues.
Am 29.01.19 um 10:58 schrieb Emmanuel Bourg:
> Le 29/01/2019 à 10:40, Per Lundberg a écrit :
>> FWIW, version 1.4.2-1 works correctly with openjdk-11-jdk version
>> 11.0.2+7-1, but it _does not_ work correct any more with Java 8
>> (openjdk-8-jdk version 8u191-b12-2)
>
> Thank you for the
Le 29/01/2019 à 10:40, Per Lundberg a écrit :
> FWIW, version 1.4.2-1 works correctly with openjdk-11-jdk version
> 11.0.2+7-1, but it _does not_ work correct any more with Java 8
> (openjdk-8-jdk version 8u191-b12-2)
Thank you for the feedback Per. What issue did you see when using
visualvm
FWIW, version 1.4.2-1 works correctly with openjdk-11-jdk version
11.0.2+7-1, but it _does not_ work correct any more with Java 8
(openjdk-8-jdk version 8u191-b12-2)
This worked correctly with 1.3.9-1 after downgrading the libnb-*-java
packages as suggested by Ben - visualvm worked fine on
18 matches
Mail list logo
