-
Notifications
You must be signed in to change notification settings - Fork 39
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
Remove the automatic module names #357
Comments
Where are these recommendations by the Spec Committee? |
We gather the analysis here: https://docs.google.com/spreadsheets/d/1g8jYG0JixO3wzZkpeyU1LMIQRhbnZ76kGtdMFE8mieE/edit#gid=0 with Websocket the only one unresolved. |
OSGi bundles "jakarta.websocket" and "jakarta.websocket.client" already existed in Jakarta EE 8 although there they also matched the old package namespace, so I recommend, we keep the automatic-module names but without the "api" so they are also aligned with the OSGi module definitions that existed before. |
Task-Url: jakartaee#357 Signed-off-by: Werner Keil <werner.keil@gmx.net>
Task-Url: jakartaee#357 Signed-off-by: Werner Keil <werner.keil@gmx.net>
Task-Url: #357 Signed-off-by: Werner Keil <werner.keil@gmx.net>
Resolved via #358 |
The automatic module name does not comply with the JPMS module naming conventions as it has "api" at the end.
Since this was not present in Jakarta EE 8 yet either, and Websocket has an additional complication by "client" and "server" APIs the recommendation by the Spec Committee is to remove it from the POM and revisit the module name (automatic or fully qualified module-info) after Jakarta EE 9.
The text was updated successfully, but these errors were encountered: