> On Aug 10, 2022, at 8:30 AM, Emmanuel Lécharny <elecha...@gmail.com> wrote: > > FTR, here is the list of projects and supported Java versions: > > Directory Project > none > > LDAP API: > Linux > Java 8, 11, 17 > Windows > java 8 > > Mavibot > Linux > Java 8, 11, 17 > Windows > Java 8 > > Server > Linux > Java 8, 11, 17 > Windows > Java 11 > > Studio > Linux > Java 11, 17 > Windows > Java 11 > > Directory BuildTools > none > > Directory-kerby > none > > Directory-jdbm > Not under git !! > > Fortress > no jenkins file >
There are pipelines for fortress builds to Apacheds and openldap: https://ci-builds.apache.org/job/Directory/ > Directory-Scimple > No jenkins ffile > > > So we have some kind of work here: > - add the windows Java 11 and 17 builds in JenkinFile > - add JenksFile for Kerby, Fortress and Scimple > - add jdbm project in git repository > > I'm not sure about the version change though. IMO, the users should be able > to use the projects with 11 and 17, no matter the version they use. The onbly > pb is for the rare who are still using Java 8. That’s what I’m referring to. There will be other ramifications, as to what packages can them be employed. For example, fortress will have to migrate jaxb to Jakarta. These are breaking changes to projects that depend, thus the suggestion to bump up a major revision to delineate the change. i.e. anyone running Java 8 will be on 2.x and before. 3.x is for Java 11 and beyond. I’ve been contemplating this jump. As you said, with 8 being EOL, now’s a good time. > > Now, Java 21 is one year away, and it comes with some very interesting > features (namely virtual threads) that may give some interesting boost in > performance. That may be for a new version of the server and API. Again we’re talking about breaking compatibility for our users. (Stating the obvious) So, if API req’s 21, fortress must also. Not sure that’s a good thing to require the latest JDK. Definitely would need to be a very good reason. A blazingly fast (and robust) solution would probably suffice :-) — Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
