Personally, I believe it does matter as you do not want to keep changing the module names especially if you are adding the Automatic-Module-Name Manifest Attribute.
For the 9.0 release, I guess it does not matter too much, but the discussion around the name is going to get more involved I suspect, and expand beyond the scope of just an artifact name based module name. For example, to simplify the end user's life, I can see having one or more aggregate modules using the spec base (jakarta.servlet) that define the various import/export/services relationships for a typical servlet app, JSP app, JSF app, etc. With that structure I would expect that we do want .api modules for every spec.
Thanks for the input!
We'll have to leave this thread open for a bit to see if we are opening a can of worms or not... ;-)
Mark, thanks for volunteering to minimally change "java.servlet" to "jakarta.servlet". If we get additional volunteering along these lines, then we could contain this minimal update for Jakarta EE 9 (authentication, authorization, servlet, and transactions).
Let's see how this discussion plays out (and get input from the Spec Committee) as to what's containable for Jakarta EE 9, or 9.1, or 10. Thanks!
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutter
Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037Oracle Java Engineering 1 Network Drive Burlington, MA 01803Lance.Andersen@xxxxxxxxxx
|
