Hi Colm,


On 03/04/2023 12:48, Colm O hEigeartaigh wrote:
Hi,

CXF migrated recently from using Apache Directory Server in the tests
to UnboundID LDAP due to a failure on JDK 20:
https://issues.apache.org/jira/browse/CXF-8809

I was a bit surprised when I checked out why to see that this issue is
fixed since almost two years but not released:
https://issues.apache.org/jira/browse/DIRSERVER-2326

What needs to be done to cut a new release? Maybe the unfixed issues
assigned to this release in JIRA can be mostly moved to the next
release? Incidentally, the OSGi tests are failing for me locally.

There are a lot of things to do if we want to cut a *perfect* release, but I think we can cut another milestone release.

I was working on fixing a few critical issues in Apache LDAP API those last weeks, and I'm done now. Still waiting for a fix for some OSGi tests that fail with maven Surefire 3.0.0 (but which work with 3.0.0-M5). This is currently being investigated by some Maven fellow.

In any case, I'm willing to cut a LDAP API 2.1.3 release in April, followed by a Server milstone (I have checked that it builds, and it's ok).

I haven't tested it with all the Java version, but I can assure that LDAP API is working with Java 8, 11 and 17:

https://builds.apache.org/blue/organizations/jenkins/Directory%2Fdir-ldap-api-pipeline/detail/dir-ldap-api-pipeline/244/pipeline

Redarding the server, we have it working in Java 17, and have some failures in Java 8 and 11, to be investigated:

https://builds.apache.org/blue/organizations/jenkins/Directory%2Fdir-server-pipeline/detail/dir-server-pipeline/270/pipeline


Colm.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


--
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
[email protected] https://www.busit.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to