|Re: [jakartaee-platform-dev] [External] : Re: module-info tests|
For specification projects, it is up to the project to add any unit tests they want. There cannot be TCK/signature level tests as there is no requirement for Jakarta EE run-times to support JPMS. The specification committee will define the requirements for valiation of the module-info.class as part of the API jar validation when the final specification is ratified.
For implementation/vendor provided API jars, there are NO requirements. An implmentation does not need to provide a module-info, and they may provide an alternate module-info. It will not be validated as part of compatibility testing.
On 10/19/21 12:53 AM, David Blevins wrote:Do we plan to ensure that anyone who provides a module-info in their APIjar does so identically to the ones produced by the Jakarta Spec project?
If one wants to provide his own implementation of the API jar, the
module-info there should be allowed to be _either_ equal/identical to
the spec project provided one _or_ a super-set of the one spec project
provides. The use case for super-set is to allow having API+Impl
"bundles" with possibly different requires (API may not need ie
java.logging but the impl may), exports (Impl may wish to export some
non-jakarta API along with jakarta API), provides/uses (Impl may define
its own extension points).
--lukas-David_______________________________________________jakartaee-platform-dev mailing listTo unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!d0UWVb3Bb8NljEqBm7HJRsb0XdbTXVummhd2fsDD3UkOt9G2Dc32tVp7BjZRkipQae8$
jakartaee-platform-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
Back to the top