The underlying issue with jdk11 support was found to be jersey (driect dependency within DW). Master has already been upgraded to 2.27, but there is an outstanding issue that will come resolved in 2.27.1 or maybe even just migrate to 2.28.
I'd recommend (and we are working similarly at my company) to have a test branch of your services or internal framework for the master 1.4.0-SNAPSHOT release so you can start on the migration path knowing that small incremental changes will still be coming. Trevor On Tue, Sep 11, 2018, 8:03 AM jeremiah adams <[email protected]> wrote: > Has there been any discussion regarding Oracle's licencing and release > cadences? Does Dropwizard plan on supporting/following the OpenJDK release > schedule or lock us into Oracle Java's release cadence. The later implies > that users would be locked into licensing the LTS version which maybe cost > prohibitive for some. > > Note that my company will have to jump to java 11 by the end of January > 2019 or start paying for support/security patches. > > Faq on the release cadence: > > > https://blogs.oracle.com/java-platform-group/update-and-faq-on-the-java-se-release-cadence > > > - jeremiah > > -- > You received this message because you are subscribed to the Google Groups > "dropwizard-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
