Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jms-dev] please take action regarding jms-api#216 (Missing OSGi Headers...)

Hi Ed,

I was under the impression thatĀ should have fixed this. It was merged and the artefact rebuild and re-staged. SeeĀ (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:


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

Back to the top