[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [glassfish-dev] Project Board
|
Hi,
Great timing indeed, thx!
I’ll try 20.3.1 out from source later tonight.
Kind regards,
Arjan
On Wednesday, February 19, 2020, Jan Supol <
jan.supol@xxxxxxxxxx> wrote:
Hi Arjan,
That's right on time, we are just in the middle of Jersey 2.30.1 release.
We put the change in (https://github.com/eclipse-ee4j/jersey/pull/4396). I took a defensive step towards HK2, just for sake, too.
Thanks,
Jan
On 19.02.2020 15:33, arjan tijms wrote:
Looks good Steve, thx!
Regarding the 6.0.0-SNAPSHOT issue, it currently fails on QuickLook tests after the CI issues have been fixed.
After a quick glance it seems to be a well know problem, comparable to what we saw in Payara when moving to version 5 and in MicroProfile with version CDI 2; it's the infamous OSGi protection against major version changes.
In this case it's jersey-gf-ejb.jar, which is protected against versions of GF having a major version number of 6 or higher. From its MANIFEST.MF:
Import-Package: com.sun.ejb.containers;version="[4.0,6)",com.sun.enter
prise.config.serverbeans;version="[4.0,6)",javax.annotation,org.glass
fish.ejb.deployment.descriptor;version="[4.0,6)",org.glassfish.intern
al.data;version="[4.0,6)",org.glassfish.internal.deployment;version="
[4.0,6)",javax.ejb;version="[3.2,4)",javax.inject;version="[1.0,2)",j
avax.interceptor;version="[1.2,2)",javax.naming,javax.ws.rs <https://urldefense.com/v3/__http://javax.ws.rs__;!!GqivPVa7Brio!LxFgyU458CXifMb8fndSZJ3Zi1UdANlok-_wELNQNrsn5V1NKuQ3Y5o8axTiHroQ$>;version="
[2.1,3)",javax.ws.rs.core;version="[2.1,3)",javax.ws.rs.ext;version="
[2.1,3)",org.glassfish.hk2.api;version="[2.5,3)",org.glassfish.jersey
.internal.inject;version="[2.28,3)",org.glassfish.jersey.internal.l10
n;version="[2.28,3)",org.glassfish.jersey.server;version="[2.28,3)",o
rg.glassfish.jersey.server.model;version="[2.28,3)",org.glassfish.jer
sey.server.spi;version="[2.28,3)",org.glassfish.jersey.server.spi.int <https://urldefense.com/v3/__http://org.glassfish.jersey.server.spi.int__;!!GqivPVa7Brio!LxFgyU458CXifMb8fndSZJ3Zi1UdANlok-_wELNQNrsn5V1NKuQ3Y5o8a_WQNra9$>
ernal;version="[2.28,3)",org.glassfish.jersey.spi;version="[2.28,3)"
Require-Capability: osgi.ee <https://urldefense.com/v3/__http://osgi.ee__;!!GqivPVa7Brio!LxFgyU458CXifMb8fndSZJ3Zi1UdANlok-_wELNQNrsn5V1NKuQ3Y5o8a3tbKih9$>;filter:="(&(osgi.ee <https://urldefense.com/v3/__http://osgi.ee__;!!GqivPVa7Brio!LxFgyU458CXifMb8fndSZJ3Zi1UdANlok-_wELNQNrsn5V1NKuQ3Y5o8a3tbKih9$>=JavaSE)(version=1.8))"
Tool: Bnd-3.5.0.201709291849
I'll update the issue and cc jansupol
Kind regards,
Arjan
On Wed, Feb 19, 2020 at 5:53 AM sawamura.hiroki@xxxxxxxxxxx <mailto:sawamura.hiroki@fujitsu.com> <sawamura.hiroki@xxxxxxxxxxx <mailto:sawamura.hiroki@fujitsu.com>> wrote:
Hi Steve,
Thank you for your suggestions, +1.
About JDK 11 support,
IMO, for the time being, I think it's better to create 1 issue for
- each problems to be solved(such as #22874,#22878,...) and
- each devtests(such as web_jsp, deployment_all, ejb_group_1,
ejb_group_2, ejb_group_3...).
And after the release of TCK 9.0.0, in addition, 1 issue for
- each test suites(such as appclient, assembly, compat12,
compat13, concurrency, connector...) and
- each problems to be solved for passing TCKs.
Thanks,
Hiroki
From: glassfish-dev-bounces@eclipse.org
<mailto:glassfish-dev-bounces@eclipse.org>
<glassfish-dev-bounces@eclipse.org
<mailto:glassfish-dev-bounces@eclipse.org>> On Behalf Of Steve
Millidge (Payara)
Sent: Wednesday, February 19, 2020 3:03 AM
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx
<mailto:glassfish-dev@eclipse.org>>
Subject: [glassfish-dev] Project Board
I have created a project board
https://github.com/eclipse-ee4j/glassfish/projects/1
<https://urldefense.com/v3/__https://github.com/eclipse-ee4j/glassfish/projects/1__;!!GqivPVa7Brio!LxFgyU458CXifMb8fndSZJ3Zi1UdANlok-_wELNQNrsn5V1NKuQ3Y5o8a7WE0NBi$>.
My suggestion is we create issues for tasks required for the 6.0
release and target them to the 6.0.0 milestone. We can then pull
all the 6.0.0 milestone issues onto the project board and track
progress that way.
Ideas for first issues, of the top of my head, are;
JDK 11 support.
1 issue for incorporation of each api
1 issue for each Compatible Implementation that GlassFIsh pulls in
e.g Tyrus, Jersey etc.
Analysis of the deployment subsystem and a series of issues of
work in this area.
1 issue for each spec compatible implementation that is a part of
GlassFish e.g. Connectors, Enterprise Beans etc.
Thoughts?
Steve
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx <mailto:glassfish-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/glassfish-dev
<https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/glassfish-dev__;!!GqivPVa7Brio!LxFgyU458CXifMb8fndSZJ3Zi1UdANlok-_wELNQNrsn5V1NKuQ3Y5o8ayjLRGpN$>