Re: [ee4j-build] Fwd: [eclipse-ee4j/jta-api] Jakarta release has wrong O

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

I don't think that bug is critical for this release, but if you can release another dot-dot version of the API to fix it that would be great.

Hopefully the spec-version-maven-plugin can catch these errors, are you using it?

Others will have to answer about the current TCK process...

Tom Jenkinson wrote on 12/6/18 6:56 AM:

Hi,

A user from the JTA community raised the topic of an OSGi bundle symbolic name being incorrect in the Jakarta EE JTA API release.

Is this something I should be looking to change? I don't think it was specifically raised as something to address yet?

If it is a change that must be made prior to GlassFish 5.1, is the process to request a TCK run still to tag @anajosep as I did previously [1]

Thanks,

Tom

[1] https://github.com/eclipse-ee4j/jta-api/pull/20#issuecomment-427812952

---------- Forwarded message ---------
From: rfelcman <notifications@xxxxxxxxxx>
Date: Thu, 6 Dec 2018 at 14:48
Subject: [eclipse-ee4j/jta-api] Jakarta release has wrong OSGi Bundle-SymbolicName (#27)
To: eclipse-ee4j/jta-api <jta-api@xxxxxxxxxxxxxxxxxx>
Cc: Subscribed <subscribed@xxxxxxxxxxxxxxxxxx>

Jakarta release of this API has wrong value of OSGi Bundle-SymbolicName in MANIFEST.MF.
Current value is javax.transaction-api but expected value could be jakarta.transaction-api .

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build