-
Notifications
You must be signed in to change notification settings - Fork 20
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
Jackson JSR353 library is using wrong module name for javax json api #7
Comments
@moquinr sounds reasonable -- I don't use module system in general, nor this module specifically, so I rely on others to find out these issues. @GedMarc any comments? Is this yet another thing that has changed over time, or did I just guess wrong module name originally? But most importantly, do you agree with the change proposed? |
Your guess would have been correct if it was using the automated module name. Honestly, I didn't think the jar would have a module descriptor in it, so I'm guessing you probably didn't either. :) |
@moquinr no, and I think there may also have been complications about multiple competing api jars with possibly conflicting settings (often seems to happen with jcp/jsr jars). But not saying there necessarily was any solid reasoning involved :) |
Looking at jar itself, yes, declared module name is "java.json" so making the change as suggested (confirmed by |
Thanks guys! |
Released in 2.12.1. |
In the jsr353 module, the javax json api module require statement is using the wrong module name, resulting in this error:
java.lang.module.FindException: Module javax.json.api not found, required by com.fasterxml.jackson.datatype.jsr353
The "correct" name (in quotes because there is no consistency in the jakarta projects on how they named the javax modules :( ) is java.json.
So it should be
rather than
The text was updated successfully, but these errors were encountered: