Date: Fri, 24 May 2019 09:06:38 +0200 From: "Michael Osipov" <1983-01-06@gmx.net> To: "Robert Huff" <roberthuff@rcn.com> Cc: java@freebsd.org Subject: Re: movinf from openjdk8 to openjdk11/12 Message-ID: <trinity-c67f1bde-295e-4bf1-ba1e-af629207a951-1558681598232@3c-app-gmx-bs17> In-Reply-To: <23783.10222.962185.577751@jerusalem.litteratus.org> References: <23783.10222.962185.577751@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert, > jakarta-commons-codec-1.10 > jakarta-commons-logging-1.2 > jakarta-commons-httpclient-3.1_1 > jakarta-commons-lang-2.6 Out of couriosity, how to do you use them if not through dependency management? > hamcrest-1.3 > junit-4.12 > apache-ant-1.10.5 > bsh-2.0.b6 > icedtea-web-1.6.2_5 > > using openjdk8. While I understand the work is not complete, > openjdk11 and openjdk12 are in the ports tree. > I am _not_ java-aware; is there a way to tell which, if any, of > those programs will not with one of those two versions? Query the website of the projects and it will tell you. I can tell you for the Apache Commons that all of the current versions are tested against Java 11, 12, 13 on the ASF Jenkins instance as well as the CI system available at GitHub. As Apache Commons member I highly advise you not use these anymore > jakarta-commons-logging-1.2 > jakarta-commons-httpclient-3.1_1 > jakarta-commons-lang-2.6 They are *not* supported anymore. Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-c67f1bde-295e-4bf1-ba1e-af629207a951-1558681598232>