[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [glassfish-dev] GlassFish 6.0.0 release still on track?
|
Indeed, hence I wondered what an EL 3.0 respin was about.
On Tuesday, December 8, 2020, Lukas Jungmann <
lukas.jungmann@xxxxxxxxxx> wrote:
EL 3.0.0 is in central.
thanks,
--lukas
On 12/8/20 1:03 PM, Lukas Jungmann wrote:
On 12/8/20 12:48 PM, arjan tijms wrote:
Hi,
On Tue, Dec 8, 2020 at 12:20 PM Lukas Jungmann <lukas.jungmann@xxxxxxxxxx <mailto:lukas.jungmann@oracle.com>> wrote:
yes, here is the test run:
https://ci.eclipse.org/jpa/job/TCK_jakarta_JPA_run/17/console
<https://urldefense.com/v3/__https://ci.eclipse.org/jpa/job/TCK_jakarta_JPA_run/17/console__;!!GqivPVa7Brio!O3nXae8qWbLt1v3mlkhvfg3h8apzFIqIk8gGxMN4WYYOA6ZWV8eHOw4sTs5N5azUWNY$>
(still
some 450 tests to go but the one failing already passed)
once it ends and passes, that binary will be promoted to central
Okay, thanks again. One more question about the EL 3.0 respin. What is that about exactly? Is that a new version of the API or the implementation?
it's a rebuild of the v3.0.0 implementation, so it contains fix for TCK failure(s); the change itself is https://github.com/eclipse-ee4j/eclipselink/pull/983 (+some cleanup in https://github.com/eclipse-ee4j/eclipselink/pull/984)
Did the version number increase there?
No, no version number changed as the implementation is the only missing piece not in central yet - 3.0.0 will get there in about an hour or so.
thanks,
--lukas
Kind regards,
Arjan Tijms
thanks,
--lukas
>
> >
> com.sun.ts.tests.securityapi.idstore.database.invalidpriorityuseforexpr.Client.testAnnotationDBIDStore_invalidpriorityuseforexpr
> >
> com.sun.ts.tests.securityapi.idstore.database.multi.Client.testAnnotationDBIDStore_multi_withLdap
>
>
> I'll take a look at these ones. Too bad the TCK doesn't show the
> actual exception there, but this is technically quite difficult
to do.
>
>
>
>
>