[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-platform-dev] module-info tests
|
On 10/7/21 11:28 AM, Thomas Watson
wrote:
That is essentially my point. At runtime we
have no requirement to run in JPMS for the containers.
Containers that do not run in JPMS should not be forced to
provide module-infos in their implementation at runtime. It
would provide no value to them nor the applications and I
argue it could limit some possible innovation at the runtime
implementation level.
Here is were my inexperience with the TCK
shows. Does the TCK signature tests run outside of the
container directly against some set of JARs provided by the
implementation?
Yes and we use the
https://github.com/jtulach/netbeans-apitest
library for doing the signature test verification.
Tom
-----
Original message -----
From: "Scott Stark" <starksm64@xxxxxxxxx>
Sent by: "jakartaee-platform-dev"
<jakartaee-platform-dev-bounces@xxxxxxxxxxx>
To: "jakartaee-platform developer discussions"
<jakartaee-platform-dev@xxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] Re: [jakartaee-platform-dev] module-info
tests
Date: Thu, Oct 7, 2021 9:43 AM
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.
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.
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.
Tom
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev