And with such a disclaimer in place, it doesn't really matter
      which option is chosen, even "do as you wish" would work (of the
      defined ones, I'd go with F though).
      
      Also, Jakarta EE 9.1 should solely be about Jakarta EE on Java SE
      11 *on the classpath* (i.e. the modulepath only contains the Java
      SE modules; anything else is on the classpath), so module names
      would still not matter.
      As I see it, bringing Java modules into the platform is a vast
      topic, and is thus unrealistic to do in Jakarta EE 9.1.
    
      
      I can still
        appreciate
        Tibor's statements though -- we need to quit adding work, no
        matter how
        small of an effort, if we want to meet our goals of delivering
        Jakarta
        EE 9 this fall.  Thanks, Tibor.
      
        
        ---------------------------------------------------
        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
      
      
      
      From:
               Werner
        Keil <werner.keil@xxxxxxx>
      To:
               jakartaee-platform
        developer discussions <jakartaee-platform-dev@xxxxxxxxxxx>
      Cc:
               Jakarta
        specification committee
        <jakarta.ee-spec.committee@xxxxxxxxxxx>
      Date:
               07/23/2020
        11:47
      Subject:
               [EXTERNAL]
        Re: [jakartaee-platform-dev]
[jakarta.ee-spec.committee][jakarta.ee-spec][jakartaee-spec-project-leads]AutomaticModuleNamesinJakarta
        EE 9
      Sent
        by:        jakartaee-platform-dev-bounces@xxxxxxxxxxx
      
      
      That’s
          not correct, because whereever the definitions of modules like
          " java.servlet",
          "java.json", etc. existed in Jakarta EE 8 this must also be
          changed
          just like the packages.
       
      See
      https://docs.google.com/spreadsheets/d/1g8jYG0JixO3wzZkpeyU1LMIQRhbnZ76kGtdMFE8mieE/edit?usp=sharing
       
      Maybe
          Scott was a bit ahead of himself sending it to ALL project
          leads, but especially
          those that already had a module declaration in Jakarta EE 8
          and have not
          changed that to "jakarta.*" must also do that. 
      Those
          with a wrong automatic module name could also be "lazy" and
          simply
          remove that, I don’t think any full module-info wasn’t changed
          or newly
          introduced correctly, and especially those must not be
          destroyed because
          many of them like Activation are used in other specs like
          Mail, so IMO
          we could throw those options at them if that is what Scott
          suggested, but
          not sure, if the project leads may vote or if they should
          simply apply
          them, Option F is the preferred one by the Spec Committee and
          also what
          I mentioned here. 
       
      Only
          8 specs would have to do anything, of these at least 4 already
          had modules
          defined in Jakarta EE 8, so they should leave them under the
          new namespace,
          the others could also just remove the automatic declaration.
       
      Werner
       
      From:
          Tibor
              Digana
            Sent: Thursday, July 23, 2020 18:00
            To: jakartaee-platform
              developer discussions
            Cc: Jakarta
              specification committee
            Subject: Re: [jakartaee-platform-dev]
[jakarta.ee-spec.committee][jakarta.ee-spec][jakartaee-spec-project-leads]AutomaticModuleNamesinJakarta
          EE 9
       
      Our
          goal was to change the license and rename the Java packages.
          Please do
          not prolong the work with more ambitions.
       
      Dňa
          št 23. 7. 2020, 16:48 Scott Stark <starksm64@xxxxxxxxx>
          napísal(a):
      I
          sent an email to the project leads list asking for feedback in
          the comments
          section of the doc that I just added.
       
      On
          Thu, Jul 23, 2020 at 4:32 AM Werner Keil <werner.keil@xxxxxxx>
          wrote:
      Thanks
          a lot, that might make it easier to decide.
       
      Werner
       
      Sent
          from Mailfor Windows 10
       
      From:
          Scott
              Stark
            Sent: Thursday, July 23, 2020 03:00
            To: Jakarta
              specification committee
            Cc: jakartaee-platform
              developer discussions
            Subject: Re: [jakarta.ee-spec.committee]
[jakartaee-platform-dev][jakarta.ee-spec][jakartaee-spec-project-leads]AutomaticModule
          NamesinJakarta EE 9
       
      Now
          there are 6 options in the "Proposals
          for Handling of Automatic-Module-Name header in Jakarta EE 9"
          document after merging changes suggested by Kevin and Werner.
       
      _______________________________________________
          jakartaee-platform-dev mailing list
          jakartaee-platform-dev@xxxxxxxxxxx
          To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
      _______________________________________________
          jakartaee-platform-dev mailing list
          jakartaee-platform-dev@xxxxxxxxxxx
          To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
       _______________________________________________
            jakartaee-platform-dev mailing list
            jakartaee-platform-dev@xxxxxxxxxxx
            To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
          
      
      
      
      _______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev