Re: OpenJDK 11 -- testing needed
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. Emmanuel Bourg [1] https://github.com/javaee/metro-jax-ws
Re: OpenJDK 11 -- testing needed
Hi, Am 20.07.2018 um 21:43 schrieb Matthias Klose: > Hi, > > OpenJDK now is feature complete, and the package in unstable should migrate to > testing soonish. I didn't do any test rebuilds with 11 yet, but I think now > it's time to start doing these. Chris West did these for 10, but doesn't seem > to be active at the moment. Is there anybody volunteering to do test rebuilds > with 11, or should we just change the default and then start fixing issues? 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. I'm also in favor of keeping OpenJDK 8 in Buster around as a fallback solution and a means to build multiple packages from source which will not be ready in time. One example is Netbeans 9 that requires OpenJDK 8 at build time but supports Java 9 and above at runtime. There are other packages where upstream continues to use Java 8 and I'm a bit tired to work around it. So in my opinion it makes sense to keep OpenJDK 8 in Buster for development and building packages as long as we make it clear that it is not supported at runtime and security-wise. You could just package the latest version right before we go into deep freeze and that's it. Markus signature.asc Description: OpenPGP digital signature
OpenJDK 11 -- testing needed
Hi, OpenJDK now is feature complete, and the package in unstable should migrate to testing soonish. I didn't do any test rebuilds with 11 yet, but I think now it's time to start doing these. Chris West did these for 10, but doesn't seem to be active at the moment. Is there anybody volunteering to do test rebuilds with 11, or should we just change the default and then start fixing issues? Matthias
