Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] package prefixes for Jakarta Batch TCK-related classes? org.eclipse.ee4j.batch ?
I had this matter discussed in today's platform call. Below is the suggestion for the naming convention:

  • [Emily] Package naming convention for TCKs?

    • Packages for TCK starts with various names, e.g. org.ibm, org.jboss, org.eclipse, jakarta.[spec].tck etc,

    • Should they be standardized? 


  • Two things need naming standard:

    • Packages

      • Suggested Naming Standard: jakarta.tck.[spec] 

      • New classes in existing TCKs should use the new name standard

    • Artifacts

      • Same group id as the spec

      • Artifact ids [foo]-tck

  • Existing TCKs may change if they like

New TCKs must use the new name standard

The above is the general consensus from the meeting. I will start a new thread conversation for others to comment on the naming convention.

Thanks
Emily


On Tue, Jan 4, 2022 at 8:17 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
I'd be in favor of the org.eclipse.jakarta.<shortname> convention suggested by Scott Kurz.  Perhaps even org.eclipse.jakarta.tck.<shortname>.

Ideally, we don't use the `ee4j` prefix as that perpetuates the blurred line between implementations and specifications.

In terms of where we make the decision, I hope we can we continue with the goal to make decisions on the list and use calls to supplement list discussion.  We had always talked about adopting the Apache perspective of "If it didn't happen on the mailing list, it didn't happen."


--
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

> On Jan 4, 2022, at 6:20 AM, Thomas Watson <tjwatson@xxxxxxxxxx> wrote:
>
> I agree we should come to some agreement on the platform call.  Although I also agree with Scott Stark that it doesn't really matter because these are not public APIs.  With that said we should at least come up with an answer going forward for some consistency.
>
> Tom
> 
> 
> 
> ----- Original message -----
> From: "Emily Jiang via jakartaee-platform-dev" <jakartaee-platform-dev@xxxxxxxxxxx>
> Sent by: "jakartaee-platform-dev" <jakartaee-platform-dev-bounces@xxxxxxxxxxx>
> To: "jakartaee-platform developer discussions" <jakartaee-platform-dev@xxxxxxxxxxx>
> Cc: "Emily Jiang" <emijiang6@xxxxxxxxxxxxxx>
> Subject: [EXTERNAL] Re: [jakartaee-platform-dev] package prefixes for Jakarta Batch TCK-related classes? org.eclipse.ee4j.batch ?
> Date: Tue, Jan 4, 2022 6:44 AM
> 
> I think it is better for us to agree on a naming convention on the platform calls so that the new packages can use the naming convention without the need to discuss over and over again. CDI tcks use org.jboss.* while some other tcks such as json-b using jakarta.json.bind.tck
> 
> Thanks
> Emily
> 
> On Sat, Dec 18, 2021 at 1:26 AM Scott Stark <starksm64@xxxxxxxxx> wrote:
> I personally don't see that it matters that much. It is not a public API used by applications. This is not something covered in https://wiki.eclipse.org/JakartaEE_Maven_Versioning_Rules, so it is undefined.
> 
> On Dec 17, 2021 at 5:11:00 PM, Scott Kurz <skurz@xxxxxxxxxx> wrote:
>> We were wondering in the Jakarta Batch  ML  https://www.eclipse.org/lists/jakartabatch-dev/msg00270.html what package prefix to use for new modules in the Batch TCK
>> and I couldn't see where this had been answered before.
>>
>> The legacy TCK uses com.ibm.jbatch.tck but what should new modules use?
>>
>> We observed the JSONB TCK using jakarta.json.bind.tck
>> https://github.com/eclipse-ee4j/jsonb-api/tree/master/tck/src/main/java/jakarta/json/bind/tck
>> but that strikes me as probably the wrong answer (unless somehow these will remain hidden in the repo;  our Batch modules, OTOH, are all published to Maven Central).
>>
>> Seems like the right answer would be one of:
>>
>>   org.eclipse.ee4j.batch
>>   org.eclipse.jakarta.batch
>>
>> Anyone know the answer?  Thanks,
>> ------------------------------------------------------
>> Scott Kurz
>> WebSphere / Open Liberty Batch and Developer Experience
>> skurz@xxxxxxxxxx
>> --------------------------------------------------------
>> 
>>
>> _______________________________________________
>> 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
> 
> 
> --
> Thanks
> Emily
> 
> _______________________________________________
> 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


--
Thanks
Emily

Back to the top