Hi all,
We discussed with Scott Kurz on the Slack channel that we should choose a good package prefix for the new code we add to the TCK.
The donated modules should probably stay with the existing com.ibm.jbatch.tck prefix, there's no value in refactoring them. But what about the newly added modules? And any future modules? Should they also use the same package prefix, or something independent,
not related to IBM?
I had a look at JAX-RS and JSON-B TCKs, and they are using the API prefix plus .tck, i.e.
jakarta.ws.rs.tck or
jakarta.json.bind.tck. If we follow that pattern, new modules should use the
jakarta.batch.tck prefix.
Do you agree with using the prefix jakarta.batch.tck for newly added modules and all future modules? Or should we continue with com.ibm.jbatch.tck? Or can anybody suggest a better prefix?
Note: this isn't about maven artifact groups. All the modules now use the jakarta.batch maven group, only artifact name changes. This is about the package names in the code inside the modules.
All the best,
Ondrej Mihályi
Senior Payara Service Engineer
Payara - Supported Enterprise
Software for Jakarta EE and MicroProfile Applications
US: +1 415 523 0175 | UK: +44 207 754 0481
----------------------------------------------------------------------------------------------------------------------
Payara is a proud recipient of the prestigious
Queen's Award for Enterprise: International Trade 2021
Payara-Tech LDA, Registered Office: Rua Nova de São Pedro no. 54, 2nd floor, room “D”, 9000 048 Funchal, Ilha da Madeira, Portugal
VAT: PT 515158674 |
www.payara.fish |
info@xxxxxxxxxxx |
@Payara_Fish
_______________________________________________