Re: [jms-dev] please take action regarding jms-api#216 (Missing OSGi Hea

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi Ed,

I was under the impression that https://github.com/eclipse-ee4j/jms-api/pull/217 should have fixed this. It was merged and the artefact rebuild and re-staged. See https://oss.sonatype.org/content/repositories/staging/jakarta/jms/jakarta.jms-api/2.0.2/jakarta.jms-api-2.0.2.pom (it has the 1.0.5 parent indicating it's the result from the 217 pull).

What is specifically still missing, or is like JSP/JSF a matter of re-running the TCK again?

Kind regards,

Arjan Tijms

On Wed, Dec 19, 2018 at 5:37 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:

Hi,

Arjan, could you please have a look at jms-api#216 and see if we can resolve this issue? It is causing CTS and/or integration errors and will block the completion of Eclipse GlassFish 5.1. Please feel free to work directly with the filer (Lukasj), or the CTS team if you have any questions or need to look at test results.

If someone else is looking into this, please assign it to yourself.

Thank you!

-- Ed