|
Hello,
Most of these issues will be fixed once all Jakarta components are included.
For issue #22539, the pull request referred to is
https://github.com/eclipse-ee4j/grizzly/pull/2015, however this PR is not included in the EE4J_8 branch and therefore will not be in GlassFish 5.1 (unless it is cherry-picked and grizzly does another release)
The JSON-P issue is resolved in 1.1.5 is has a PR for GlassFish (#22651). The other OSGi ones are likely to be fixed by 5.1 final release as things are merged.
Jonathan Coustick
On 06/12/2018 22:27, Bill Shannon wrote:
The focus for the Eclipse GlassFish 5.1 release is simply to replace all the Oracle components with Eclipse components and for the result to pass the Java EE 8 CTS.
If there's bugs in Oracle GlassFish 5.0.1 that also exist in Eclipse GlassFish 5.1, that's ok. Obviously we'd like any serious bugs to be fixed, but that's not the primary focus. Bug-for-bug compatible is fine. If new bugs have been introduced since 5.0.1,
we need to evaluate their severity and the cost to fix them.
Hopefully there will be an Eclipse GlassFish 5.1.1 or 5.2 release that can apply more polish and clean up some of these more serious bugs.
For #22539, the discussion mentions a Pull Request, but I don't see it. A Pull Request against Eclipse GlassFish to fix this issue would make it more likely that the issue would be fixed in 5.1, especially if the fix comes with a unit test or dev test verifying
the fix.
Ditto #22635, which doesn't seem serious, but a PR would help.
I wouldn't expect TCK testing to detect either of the above bugs.
Paul Stanley wrote on 12/6/18 7:00 AM:
Hello,
I’m just wondering what the status of the Glassfish project is? The 5.1.0RC1
release at the end of October, but since then there doesn’t appear to be any attempt to fix any of the issues which have been raised. For
instance
the memory leak in the http stack (#22539). I’ve also come across
of a number of features that simply do not work due to incorrect or missing
osgi
meta-data.
These include JSON-P, ldap-booster-pack-extensions
(#22635), jersey-client and the tyrus-client.
I would have assumed that these
will have been picked up by the Jakarta
TCK testing, but I've not seen anything.
I
realise that everyone is working flat out
for the 5.1.0 release so I'm not expecting miracle's,
but I was wondering if there was a list of critical issues
that will be addressed?
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
|
