Lukas Jungmann

@mkarg Commented I can't believe it is five years since i reported it. Are there any plans to add this reall small change?

In my opinion and based on the original intent of the requirement for JPMS descriptors in the spec API artifacts and their testability > "there is no requirement around testing...

> Is the Activation dependency on JPMS explained [..] Given [EFSP 1.2](https://www.eclipse.org/projects/efsp/?version=1.2#efsp-terms) adopted by [JESP 1.3](https://jakarta.ee/about/jesp/) defines *Specification* as: _A collection of Application Programming Interface (API) definitions, descriptions of semantic...

> ^ seems to describe the lookup that is expected by the Activation Java Doc description but it looks like the actual lookup action is in [jakarta.activation.FactoryFinder](https://github.com/eclipse-ee4j/jaf/blob/master/api/src/main/java/jakarta/activation/FactoryFinder.java) which is not...

> There was a discussion and agreement on the platform call back on October 19th, 2021 right, this testing was merged ~week before that to cover the outcome from 2021-06-29...

as I see it, the API for Activation spec defined by the platform is different from the one defined by its standalone version (applies to all specs) and therefore possible...

resolution: * for the platform runs, new test configuration config file (`ts-platform.jte`) gets created * `UnnamedModule_Test` gets updated to include `...getModule().isNamed()` check before checking the actual name * instructions in...

Done

See https://github.com/jakartaee/jaf-tck/pull/59#issuecomment-1476809179

should be OK now