Repository navigation
Updated Grizzly dependencies - fixed jpms - #6093
Conversation
Signed-off-by: David Matějček <david.matejcek@omnifish.ee>
- M1 depended on snapshot parent Signed-off-by: David Matějček <david.matejcek@omnifish.ee>
- M1 depended on snapshot parent Signed-off-by: David Matějček <david.matejcek@omnifish.ee>
|
@dmatej Thank you for this contribution. As I am a new committer on Jersey I have one question. Do we typically just merge directly our own commits without waiting for any review comments of other committers? |
|
Yes indeed. Of course after commit checking and reviews are still appreciated, and we can do new commits to fix anything if needed then. |
Some branches are protected, some not, I don't like it too much, but when the problem is clear and well tested, I can do that from time to time. In general, Automated module names cause more problems that they resolve, and historically were just a temporary solution. |
Grizzly NPN API 2.0.0 used just automatic module name and did not declare any module-info.java. 2.0.1 fixed that.