Re: [glassfish-dev] GlassFish status

["sawamura.hiroki@xxxxxxxxxxx" <sawamura.hiroki@xxxxxxxxxxx>]

Hi

Thanks all.
I'll resolve the conflicts so that we can merge the following JDK11 work at any time.
https://github.com/eclipse-ee4j/glassfish/pull/23019
# Note that GlassFish will only run with JDK 11 if this PR is merged.(Still compile with JDK 8)

> Arjan
I'm a little concerned that the "web_jsp" test has been removed from the list of tests on Jenkinsfile.
- All tests were temporarily removed: 
  https://github.com/eclipse-ee4j/glassfish/commit/8cefb6305a8676c6c03881ad499b1461f643fe5c#diff-58231b16fdee45a03a4ee3cf94a9f2c3
- Dropped web_jsp(?): 
  https://github.com/eclipse-ee4j/glassfish/commit/0dea810da59f757059b1b424fc78060a44461fba#diff-58231b16fdee45a03a4ee3cf94a9f2c3

Thanks
Hiroki


From: glassfish-dev-bounces@xxxxxxxxxxx <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of arjan tijms
Sent: Wednesday, June 10, 2020 8:06 AM
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: Re: [glassfish-dev] GlassFish status

Hi,

As of https://github.com/eclipse-ee4j/glassfish/pull/23087 the Jenkins controlled tests are starting to run again as well. I opted to begin with cdi_all which are 115 tests touching CDI, but also Enterprise Beans and Persistence.



See: https://ci.eclipse.org/glassfish/job/glassfish_build-and-test-using-jenkinsfile/job/PR-23087

Kind regards,
Arjan


On Tue, Jun 9, 2020 at 4:59 PM Scott Marlow <mailto:smarlow@xxxxxxxxxx> wrote:


On Tue, Jun 9, 2020 at 9:22 AM Steve Millidge (Payara) <mailto:steve.millidge@xxxxxxxxxxx> wrote:
All,
 
Just a heads up that the final upstream project awaiting a patch has been merged.

+1, congratulations all!

FYI, I just created https://github.com/eclipse-ee4j/glassfish/issues/23085 for a failure (running examples) due to javax.resource.spi.security.GenericCredential still used, possibly in glassfish6/glassfish/lib/schemas/connector_1_7.xsd & glassfish6/glassfish/lib/dtds/connector_1_5.dtd.  Sorry for the late note about this and issue, but we are just arriving at the point now where we can see this problem.  

I'll run again with the latest GlassFish master source.

Scott
 
 
Master branch now;
• Has moved to the Jakarta namespace
• Builds
• Runs without OSGI errors
• Can deploy smoke test application in the Jakarta namespace via asadmin
• Can deploy smoke test application in the Jakarta namespace via admin console
• Passes the Quick Look tests.
 
At this point I am going to tag it as a M1 milestone for the Jakarta EE 9 milestone release. If anybody objects let me know. I will try to tag it tomorrow.
 
Next big piece of work post the Jakarta EE 9 milestone is to get GlassFish building and running on JDK 11. 
Also we have to get GlassFish 6 through the Jakarta EE TCK.
 
Thanks All
 
 
Steve
_______________________________________________
glassfish-dev mailing list
mailto:glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev
_______________________________________________
glassfish-dev mailing list
mailto:glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev