The company that I'm working for have the same experience. We've been running Dropwizard 1.3.x on Java 11 in production for a couple of weeks now. The only thing that I've heard isn't working is Jersey component scanning (environment.jersey().packages()).
On Thursday, November 8, 2018 at 9:45:27 PM UTC+1, [email protected] wrote: > > Well, I read about many issues with Dropwizard deps and Java 11. So I > figured since it seemed no bueno that I'd give it about 10 minutes to make > it work out of curiosity. I don't know why but everything works great. This > is an app with Jackson, JDBI, Flyway, and Jersey. I kept my maven exactly > the same, just bumped the compiler up to 11, rev'd the javadoc plugin, and > added a couple of dependencies for the usual stuff like: java.xml.bind and > javax.activation. I made sure deps were up to date. I didn't change shade > at all. Everything just seems to work fine (just a warning because > afterburner uses a deprecated internal). Oh and I explicitly register my > resources just as a matter of preference. > > Could this be? Am I missing something that will bite me later? Near as I > can tell, a 10 minute investment gave me a Java 11 micro-service. I'm > missing something, right? I at least thought going from Java 8 to Java 11 > I'd have issues with Shade, but no. > > > -- You received this message because you are subscribed to the Google Groups "dropwizard-user" 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.
