[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jakartaee-tck-dev] Relaxing signature testing
|
Hi,
I'd like to propose we relax the signature testing for some specific
scenarios.
This proposal was triggered by this TCK issue:
https://github.com/eclipse-ee4j/jakartaee-tck/issues/643
Vendors providing their own API JARs may wish to add annotations such as
aQute.bnd.annotation.spi.ServiceConsumer which are required if using BND
to generate correct OSGI metadata.
These annotations have no runtime impact and are, effectively,
transparent to API clients.
Conversely, it is possible an API project could add such an annotation
but a vendor providing their own API does not.
The proposal is that we create a list of annotations that should be
ignored when performing the signature tests for the TCK.
The initial list (based on those Tomcat 10 is currently using) of
proposed annotations to ignore is:
aQute.bnd.annotation.spi.ServiceConsumer
Annotations would have to be confirmed as having no runtime impact
before they could be added to this list.
The alternative approach, in this instance, is to add these annotations
to the Jakarta provided API JARs and require any vendor provided API
JARs to use the same annotations. However, I suspect that there will be
other annotations associated with other build time tools that will fall
into this category over time and that it will not always be appropriate
to include the annotation in the Jakarta provided API JARs.
Thoughts?
Mark
