-
Notifications
You must be signed in to change notification settings - Fork 22
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
Upgrade Dropwizard to 2.x #61
Comments
Thanks for bringing this up. Currently dropwizard-guicier uses jersey2-guice in order to make HK2 and Guice work together. However, this project is abandoned and the repo is archived. Luckily, Jersey no longer requires HK2 and the dependency injection implementation is pluggable. I've started working on a Guice-based implementation in this repo: https://github.com/HubSpot/jersey2-guicier Once that's in a usable state, it should be a lot easier to upgrade to newer versions of Dropwizard/Jersey and it should hopefully fix a lot of the issues caused by using both HK2 and Guice |
👋
Update? |
I've been working on jersey2-guicier intermittently, however the API that you need to implement is pretty tied to HK2. I have most of the tests passing, but there are still a bunch of Guice errors when trying to actually use it. |
Is there some date when library with Dropwizard 2.0 support will be released? |
@Alexander-Paeshin I think the answer lays somewhere in the second comment. Specificallly, this project is abandoned and the repo is archived |
Which, btw, @jhaber - this repo is not archived. |
@OneCricketeer @jhaber was referring to this repo -> https://github.com/Squarespace/jersey2-guice (in context to his earlier statement about that project. |
I did find that https://github.com/xvik/dropwizard-guicey (another guice+dropwizard library) does support 2.x now. If upgrading is important for folks maybe migrating to this library which has had more regular contributions is in order... last commit here was back in August. |
Dropwizard 1.3.x has had many upgrades.
Dropwizard 2.0 is also out now.
The text was updated successfully, but these errors were encountered: