Re: OpenJDK 11 -- testing needed

[Matthias Klose]

On 20.07.2018 23:28, Emmanuel Bourg wrote:
> Le 20/07/2018 à 22:14, Markus Koschany a écrit :
> 
>> I think the sooner we make OpenJDK 11 the default the better. This makes
>> it more likely that we detect runtime issues before the freeze. I
>> suppose there will be some FTBFS fallout again but I expect it to be in
>> the same range when we switched from 9 to 10.
> 
> Java 11 no longer contains JAX-WS (the javax.xml.ws and javax.jws
> packages) and we don't have a replacement yet. This will affect at least
> Spring, Tomcat and Netbeans. I started packaging the standalone JAX-WS
> implementation [1], one new dependency is already in sid (saaj), another
> one is in the NEW queue (jaxws-api), and 6 more have to be uploaded
> (javax.jws, gmbal, gmbal-pfl, gmbal-commons, metro-policy and mimepull).
> These packages are ready but need some polishing (proper package
> description and copyright review).
> 
> For a smooth transition I think we should switch the default JRE to
> OpenJDK 11 once jaxws lands in sid.

this has now landed. Anything else to update before we do the switch?

Matthias

Re: ca-certificates-java 20180413

[Vincent Privat]

It was painful to wait this long (3 months) but Ubuntu maintainers have
finally backported and released the fix 1 hour ago. Finally we won't be
spammed by this error anymore :)

2018-05-04 22:45 GMT+02:00 Emmanuel Bourg :

> Le 04/05/2018 à 22:27, Vincent Privat a écrit :
>
> > Thank you Emmanuel for fixing #894979 in ca-certificates-java 20180413.
> > As you can guess, this bug impacts a lot of JOSM users on Ubuntu 18.04.
> > Do you know when the new package version will be available for bionic? I
> > wonder if we should do something upstream or tell our users to patiently
> > wait for the update.
>
> You can tell them to be patient, the update is planned but has been
> delayed by a conflict:
>
>   https://launchpad.net/bugs/1769013
>
> Emmanuel Bourg
>
>