There is work under way to improve how CTS tests
are initiated. For now, follow the process
outlined on the TCK readme:
https://github.com/eclipse-ee4j/jakartaee-tck
(at the top of README.md)
Any questions comments or suggestions about the
CTS and TCK execution process should be addressed
to @anajosep and @bhatpmk (I've added them to this
message, explicitly)
Our goal is to have Eclipse GlassFish 5.1, be as
close a match to the final Java EE GlassFish
release (5.0.1) as possible. It would be
preferable (in my opinion anyway) to hold off on
anything that isn't super critical. We think this
will provide a better transition capability for
legacy Oracle GlassFish users to migrate over to
Eclipse GlassFish (i.e. if it runs on Oracle
GlassFish 5.0.1, it should run exactly the same on
Eclipse GlassFish 5.1).
We will begin the process for 5.2 as soon as 5.1
is done. We are trying to get 5.1 done so that we
can release it in January. Changes like you
describe below, could be done in the component
master branch (or any branch other than EE4J_8).
-- Ed
On
12/6/2018 10:52 AM, Bill Shannon wrote:
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
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
_______________________________________________
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