-
-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dropwizard 3 support #307
Comments
I need to get the master branch built and released with 2.1.6, then I’ll rename the branch to 2.1.x, and create a 3.0.x branch for these updates |
Please, update also branch 2.0.12-1 to support Dropwizard 3. |
Dropwizard 3.0.x will be updated in a 3.0.x branch. If anyone would like to submit a PR against master to fix the failing tests, that will greatly speed up the process toward getting new versions released. All versions will be published to Maven Central. |
Never mind. I migrated to the version 2.1.4-1 and dropwizard-swagger is the only thing that is holding me back from migration of my project to Dropwizard 3. |
The #310 should do it. |
I published v3.0.0-1 yesterday |
Dropwizard 3 has been released, but this changes some of the package declarations.
E.G.
io.dropwizard.Configuration
is nowio.dropwizard.core.Configuration
.https://www.dropwizard.io/en/release-3.0.x/manual/upgrade-notes/upgrade-notes-3_0_x.html#dropwizard-package-structure-and-jpms
Is it possible for
dropwizard-swagger
to be upgraded to use this?The text was updated successfully, but these errors were encountered: