Re: [jakartaee-platform-dev] [jakarta.ee-spec][jakarta.ee-spec.committee

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Thanks, Scott,
Based on your
last
comment in this Issue,
did you end up changing to "java.inject" as the AMN for Jakarta
EE 8?  Or, did you leave it with "jakarta.inject"?  I
don't think it matters either way, just curious.  I'm going to update
Werner's spreadsheet to indicate that it was part of "Java EE 8"
since you have a released version of an AMN and the end result should be
"jakarta.inject" for Jakarta EE 9.  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



From:
       Scott
Stark <starksm64@xxxxxxxxx>
To:
       Jakarta
specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Date:
       07/27/2020
12:13
Subject:
       [EXTERNAL]
Re: [jakarta.ee-spec]        [jakartaee-platform-dev][jakarta.ee-spec.committee][jakartaee-spec-project-leads]AutomaticModuleNamesinJakartaEE9
Sent
by:        jakarta.ee-spec-bounces@xxxxxxxxxxx

---

The DI AMN was added in response to this
issue:
https://github.com/eclipse-ee4j/injection-api/issues/14

However, it really should have been java.inject.

The fact that users are asking for module
names brings up the issue of the usage of these api jars outside of the
platform releases. An api jar that has one of its targets being Java SE
usage needs to be able to evolve to adapt to the runtime users are making
use of.



On Mon, Jul 27, 2020 at 9:09 AM Werner
Keil <werner.keil@xxxxxxx>
wrote:
Kevin,
 
Hopefully Scott can help with that.
 
Jakarta Inject is particularly weird,
because ist automatic-module-name in the ee8 branch https://github.com/eclipse-ee4j/injection-api/blob/ee8/pom.xmlalready suggested it had "jakarta.inject”
but the 1.0 JAR in MavenCentral has an almost empty META-INF with no such
thing as a module declaration, but it released a 1.0.1 patch release this
year with the module declaration.
Its codebase/branch
and binaries don’t seem to match, please ask Scott to sort it out, IMO
based on the 1.0 state it should be removed.
 
Jakarta Validation
had "java.validation” in its 2.0.2 from August 2019 so that release
should be part of Jakarta EE 8 and it seems good to go. I updated the In
EE 8 and Issue columns accordingly. 
 
Werner
 
Sent from Mailfor Windows 10
 _______________________________________________
jakarta.ee-spec mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec