Agree, Lance. That's
why I don't want to push this into the Jakarta EE 9 schedule. We
may come up with what we think is the right answer, but until we really
dive into the JPMS impact across the Jakarta EE board, we'll probably have
to make changes later. I would prefer to leave things as-is for Jakarta
EE 9 -- except for maybe the four items we have identified as getting rid
of the 'java' prefix. --------------------------------------------------- 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
Andersen <lance.andersen@xxxxxxxxxx> To:
developer discussions <jakartaee-platform-dev@xxxxxxxxxxx> Cc:
Spec Project Leadership discussions <jakartaee-spec-project-leads@xxxxxxxxxxx>,
Jakarta specification discussions <jakarta.ee-spec@xxxxxxxxxxx> Date:
Re: [jakartaee-platform-dev] [jakarta.ee-spec] [jakartaee-spec-project-leads]Automatic
Module Names in Jakarta EE 9 Sent
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.
On Wed, Jul 22,
2020 at 8:06 AM Kevin Sutter <sutter@xxxxxxxxxx>
wrote: 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!