There is an issue in glassfish-hk2 which is preventing the glassfish server from starting in Windows environment
using asadmin commands.
https://github.com/eclipse-ee4j/glassfish/issues/23303
I fixed the issue in glassfish-hk2 repository.
https://github.com/eclipse-ee4j/glassfish-hk2/issues/535
https://github.com/eclipse-ee4j/glassfish-hk2/pull/536
This issue was not present in Glassfish-6.0.0-RC2 release and was introduced in Glassfish-6.0.0-RC3 when hk2-api
was moved from 3.0.0-M2 to 3.0.0.
Thanks
Hussain
From: glassfish-dev-bounces@xxxxxxxxxxx
<glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of
arjan tijms
Sent: Thursday, December 24, 2020 7:49 PM
To: Guillaume Smet <guillaume.smet@xxxxxxxxx>
Cc: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>; Scott Stark <sstark@xxxxxxxxxx>
Subject: Re: [glassfish-dev] GlassFish 6.0.0 release still on track?
Great, thanks!
It passed the build and basic tests for GF, now running the full TCK against it.
7.0.0.Final is available on Maven Central.
Great, thanks for the update! I'll try a new build for GF when it's ready then ;)
Funny you ask just now, I'm finalizing the last PR I want to get in the Final as we speak.
Hopefully, I will release it today and it will be available in Maven Central tomorrow morning.
Hi,
Guillaume, do you know whether there's a Hibernate Validation final planned for this year still?
CR1 is available on Central.
Yes, that's right, and indeed, we can't stage a final based on that. But we can stage a test version and at least run the TCK against that. Alternatively, the GF job(s)
can use their own local settings.xml which contains the staging repo. I'll do some experiments to see what's easiest.
We should probably assume though that we're indeed not going to release 6.0.0 tomorrow, so that's a small failure. But it should not be terrible as we do have the RC out.
To do that you will have to make a PR to add the JBoss repo into the GlassFish poms. I’m not sure
we should build a final for staging based on that change?
Hi,
To release to central all dependencies should be in central indeed, but using the JBoss staging
repo we can at least start running the TCK. I'm also not sure whether we make it in time, it would have been a whole lot better if we had CR1 last friday, but it is what it is.
I think we need to get into central so that source is buildable by anyone before we stage a release.
Once there we can build a staged 6.0.0 to run the TCK against.
Personally I don’t think we will make it in time for tomorrow as the TCK will take a while to run
but 6.0.0 can be staged tomorrow.
Steve
Hi,
Thanks! That's the same as my Amsterdam time ;)
Steve and others, what do you think, do a release of GF 6.0 during/just before the livestream then?
Meanwhile, if CR1 available in a staging repo so we can run the TCK with that?
I should have been more precise: my morning Paris time :).
I pinged Scott to make him aware CR1 was coming.
When things are synced from JBoss Nexus to Central is an unsolved mystery but what I can say from
experience is that they should be available on Central tomorrow in the morning.
Hi,
WRT Hibernate Validator I noticed a CR1 has been committed:
Has this already been pushed out to Central or is planned for today?
Great, thanks for the update.
@Scott wrt Hibernate Validator you said an RC/CR will be out next week, but could that be on Monday
at the latest? As GlassFish 6.0.0 was supposed to be available before the Jakarta livestream, which is Tuesday.
Thanks I’m pushing final versions of jsktemplating and woodstock
Ultimately I think it depends on whether the rest of the team is comfortable releasing without
all components at final.
JSF Templating and Woodstock I can probably push this weekend to final. We are still waiting for
some other components to go final see
Implementation Component Tracking - Google Sheets
Major components we are waiting for final are; Eclipselink, Weld, Hibernate Validator, OpenMQ (final
is staged), JBatch.
I'm about to push OpenMQ to central, so it should land there today.
Weld is not going final before this release, but if I'm not mistaken Red Hat uses a slightly different
approach to finals as GlassFish is using, meaning that CR/RC versions are more common. 4.0.0.CR1 is now in Maven, which is being used by GlassFish now.
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original
message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law,
this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.
|
