Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] module-info tests

If your point is just about that we should only test the API jars from the specification project release for the module-info, and not in general during compatibility testing because we don't have a requirement for JPMS in the containers, that is valid, and one I probably agree with.

On Oct 7, 2021 at 9:34:41 AM, Scott Stark <starksm64@xxxxxxxxx> wrote:
Implementations are not required, but if they do, then how do you certify? Right now the TCK signature tests look to the jars/content provided by the implementation under test. If they have their own versions of the API jars, they need to pass the same requirements as the specification project producing the API jars.

On Oct 7, 2021 at 9:24:36 AM, Thomas Watson <tjwatson@xxxxxxxxxx> wrote:
I did not intent to suggest that apps are only allowed to be compiled against the API JARs from Jakarta projects.  I was asking if implementations are required to provide to such JARs for development purposes?  Don't get me wrong, implementations should be allowed to provide such JARs to allow them to provide various developer experiences as they see fit.  Open Liberty certainly does provide such JARs for developers to compile against also.  I do think such JARs should conform to the module-info requirements from Jakarta.  But I don't think the specification requires an implementation to provide such JARs for the developer to compile against. 
If implementations are not required to provide API JARs for compilation/development purposes then I do not see the point of the TCK testing for module-info classes against the implementation.  On the other hand the Jakarta build of the API JARs should contain a test that validates they are providing the correct things.


Back to the top