You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it will bring the recent javassist: not sure if it would be a problem for jersey (which suppose to use the older version). Anyway, you'll need a new javassist in any case if you need to work on recent JDKs (and I know there were successful migrations to jdk17, so probably not a problem).
I'm asking because release for the old branch would require infrastructure updates (to be able to release at all). Not very hard to do but will take time. So if there is no real need for this version I would prefer to not doing it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I need to know if there are still people using guicey 4.x (dropwizard 1.3) who require fixes for:
Failed to analyze guice bindings
exception #160 (lambda guice modules support)And maybe #178 (jdk 16 compatibility for jdbi3). This one could be easily fixed manually by updating:
implementation 'ru.vyarus:guice-ext-annotations:1.4.0
But it will bring the recent javassist: not sure if it would be a problem for jersey (which suppose to use the older version). Anyway, you'll need a new javassist in any case if you need to work on recent JDKs (and I know there were successful migrations to jdk17, so probably not a problem).
I'm asking because release for the old branch would require infrastructure updates (to be able to release at all). Not very hard to do but will take time. So if there is no real need for this version I would prefer to not doing it.
Beta Was this translation helpful? Give feedback.
All reactions