[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [glassfish-dev] Status of GF7
|
And yet omnifish-concurrent aka
omniconcurrent must get rid of cyclic dependency on GlassFish. I
am working on that this week.
If I remember well, Maven Central
prohibits two things: cyclic dependencies and dependency on
snapshot version.
It would be good also to merge all
waiting PRs for Standard Taglibs and release it, because last week
GF failed the TCK several times on several environments and passed
after reexecution - on some environments it was well reproducible,
on some less (on my 16 core laptop with Xeon nearly always). I
created PR, with that it passed always.
https://github.com/eclipse-ee4j/jstl-api/pull/235There is more work to do, but even in
this state it is better.
David.
On 26. 09. 22 11:01, Piotr Żygieło
wrote:
We need to release GlassFish 7.0.0 from 7.0.0-M8 which was approved by the specification committee. Is there any extra work left for that?
1. shoal has to be released (currently staged version 3.0.0-M1 depends
on unreleased grizzly 4.0.0-M1) and GF should upgrade to new one
2. exousia (2.1.) could be promoted to central
3. jakarta.mvc has to be released -
https://projects.eclipse.org/projects/ee4j.mvc/reviews/2.1-release-review
- at this moment review is ongoing
4. krazo (3.0.0) could be promoted to central
--
https://www.eclipse.org/projects/handbook/#ip-other-projects:
A release of one project should never include unreleased content from another project.
--
David Matejcek | OmniFish
david.matejcek@xxxxxxxxxxx | +420 777 601 682
