-
Notifications
You must be signed in to change notification settings - Fork 89
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
Fixes #201 - Java JPMS modules. #204
Conversation
Added Automatic-Module-Name: javax.servlet.api to the MANIFEST. Signed-off-by: Simone Bordet <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
My understanding is that the module name should be |
Should be on what basis? This name was chosen to align (as closely as possible) to the OSGI bundle name of "javax.servlet-api". (See #201) |
I don't have a personal preference, for me both are valid. About the link with OSGi, it's true that the symbolic name resemble the module name, but that's about it (and they are different anyway). I'd be happy to update the PR if we reach a consensus on a different module name. It will be important that they are consistent though. We don't want the Servlet module to be the only one that has E.g. what is the proposed module name for CDI, JSP, JPA, etc.? |
I can't find an official document, but I recall there was some discussion about this during Java EE 8 development, and the Oracle recommendation was to use "java" instead of "javax" for module names. The reason is that there's no need to distinguish "core" vs "extension" modules anymore, which was the reason to add the "x" suffix. All Java SE modules, even the ones with "javax" packages, are named "java.*". In addition to this, and given that package names must be unique between modules, the general recommendation is to use the top level package as the module name. The last published versions of JSON-P, JSON-B, JAX-RS, JPA and I think JTA and JAXB already adopted this convention. |
@jodastephen wrote this comment in favor of @jodastephen do you recall if there was a discussion about module names starting with |
I believe I've seen something official that says JCP spec modules should use |
It should be java.servlet. (Really, it should be decided by the Jakarta EE Specification Committee |
Updated Automatic-Module-Name to "java.servlet" after discussion. Signed-off-by: Simone Bordet <[email protected]>
I have updated the PR to |
Added Automatic-Module-Name: javax.servlet.api to the MANIFEST.
Signed-off-by: Simone Bordet [email protected]