Okay I had screwed up this release two fold: a) I accidentally made a 22.2 release, see user list for discussion about renaming those folders to 22.2-mistake to avoid causing problems downstream b) The prior 22.1 build was one of those that failed over JDK issues so we only have partially
I have reverted the blog post to draft and will try again. -- Jody Garnett On Thu, 21 Nov 2019 at 23:32, Jody Garnett <jody.garn...@gmail.com> wrote: > Updated OracleJDK 8u202 build artifacts are here: > https://build.geoserver.org/view/release/job/geotools-release/218/artifact/build/release/distribution/22.1/ > -- > Jody Garnett > > > On Thu, 21 Nov 2019 at 11:44, Jody Garnett <jody.garn...@gmail.com> wrote: > >> Testing the OpenJDK generated artifacts: >> >> - userguide - docs are complete, README.html links are correct, LICENSE >> included, the quick search even works >> - doc - just contains apidocs folder (I expected a README or something) >> - bin - everything is fine (both LICENSE.md and LGPL.md are included but >> whatever) >> - project - builds fine >> >> With this in mind I would like to go to the next step of releasing GWC >> -- >> Jody Garnett >> >> >> On Thu, 21 Nov 2019 at 11:07, Jody Garnett <jody.garn...@gmail.com> >> wrote: >> >>> Upgrading to Oracle 221 produces our URLsTest failure >>> (java.net.MalformedURLException: Illegal character found in host: '/') >>> which Andrea has already discussed. >>> >>> I am going to stick with OpenJDK for this release. >>> -- >>> Jody Garnett >>> >>> >>> On Thu, 21 Nov 2019 at 08:56, Torben Barsballe < >>> torbenbarsba...@gmail.com> wrote: >>> >>>> Looking at the list of options "Java SE Development Kit 8u221" >>>>> and "Java SE Development Kit 8u202" are listed but not 8u212. >>>> >>>> >>>> I wonder if 8u212 got removed from the list of versions and the >>>> installer automatically changed to the latest LTS? >>>> I'd lean towards switching to OpenJDK 8u212 for the build, especially >>>> if we can't expect the oracle versions to stick around. >>>> >>>> We already test on Oracle via Travis, but we should probably still keep >>>> an Oracle install around on Jenkins if its needed for specific jobs for >>>> some reason; I see no issue with switching to 8u221 for that (You should be >>>> able to just rename / update the existing oracle entry in this case). >>>> >>>> Cheers, >>>> Torben >>>> >>>> On Wed, Nov 20, 2019 at 10:30 PM Jody Garnett <jody.garn...@gmail.com> >>>> wrote: >>>> >>>>> Digging into the build server configuration Java Installations I can >>>>> confirm that Oracle JDK 8u212 is set to "Java SE Development Kit 9.0.4"! >>>>> Looking at the list of options "Java SE Development Kit 8u221" >>>>> and "Java SE Development Kit 8u202" are listed but not 8u212. >>>>> >>>>> Releasing with openjdk8 works, build artifacts here >>>>> https://build.geoserver.org/view/release/job/geotools-release/216/ >>>>> >>>>> I would like feedback from others before defining an "Java SE >>>>> Development Kit 8u221" entry (perhaps we are just happy with openjdk) >>>>> -- >>>>> Jody Garnett >>>>> >>>>> >>>>> On Wed, 20 Nov 2019 at 21:59, Jody Garnett <jody.garn...@gmail.com> >>>>> wrote: >>>>> >>>>>> This is a very confusing snippet - it appears that the java version >>>>>> is 9.0.4, while the runtime is Oracle_JDK_8u212? >>>>>> >>>>>> maven/java settings: >>>>>> [1mApache Maven 3.6.0 [m >>>>>> Maven home: /usr/share/maven >>>>>> Java version: *9.0.4*, vendor: Oracle Corporation, runtime: >>>>>> /tmp/jenkins-3858afaa/tools/hudson.model.JDK/Oracle_JDK_8u212 >>>>>> Default locale: en, platform encoding: UTF-8 >>>>>> OS name: "linux", version: "4.15.0-1021-aws", arch: "amd64", family: >>>>>> "unix" >>>>>> MAVEN_FLAGS=--batch-mode -Dfmt.skip=true >>>>>> >>>>>> >>>>>> >>>>>> The previous release had the expected 1.8.0_212: >>>>>> >>>>>> maven/java settings: >>>>>> [1mApache Maven 3.6.0 [m >>>>>> Maven home: /usr/share/maven >>>>>> Java version: *1.8.0_212*, vendor: Oracle Corporation, runtime: >>>>>> /tmp/jenkins-b3e7745d/tools/hudson.model.JDK/Oracle_JDK_8u212/jre >>>>>> Default locale: en, platform encoding: UTF-8 >>>>>> OS name: "linux", version: "4.15.0-1021-aws", arch: "amd64", family: >>>>>> "unix" >>>>>> MAVEN_FLAGS=--batch-mode -Dfmt.skip=true >>>>>> >>>>>> >>>>>> -- >>>>>> Jody Garnett >>>>>> >>>>>> >>>>>> On Wed, 20 Nov 2019 at 20:44, Jody Garnett <jody.garn...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> I am in the process of releasing: >>>>>>> >>>>>>> GeoTools 22.1 >>>>>>> >>>>>>> - revision: 1946a521f6a307baa27799220405b766bb81f3e2 >>>>>>> - jira: >>>>>>> >>>>>>> https://osgeo-org.atlassian.net/secure/ReleaseNote.jspa?projectId=10001&version=16768 >>>>>>> - blog: >>>>>>> >>>>>>> https://www.blogger.com/post-preview-auth.g?postID=6887264291526178273&blogID=116830172286767929 >>>>>>> >>>>>>> >>>>>>> Blog post is drafted for review. >>>>>>> >>>>>>> Initial attempt 215 >>>>>>> <https://build.geoserver.org/view/release/job/geotools-release/215/> >>>>>>> has failed on javadoc generation which was unexpected. >>>>>>> -- >>>>>>> Jody Garnett >>>>>>> >>>>>>> >>>>>>> On Wed, 20 Nov 2019 at 10:00, Jody Garnett <jody.garn...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> With no outstanding requests I am ready to start the geotools >>>>>>>> release process. >>>>>>>> -- >>>>>>>> Jody Garnett >>>>>>>> >>>>>>>> >>>>>>>> On Sun, 17 Nov 2019 at 21:34, Jody Garnett <jody.garn...@gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> The GeoTools 22.1 release is scheduled >>>>>>>>> <https://github.com/geoserver/geoserver/wiki/Release-Schedule> >>>>>>>>> for this week. If you have any fixes or pull requests this is your >>>>>>>>> reminder >>>>>>>>> :) >>>>>>>>> -- >>>>>>>>> Jody Garnett >>>>>>>>> >>>>>>>> _______________________________________________ >>>>> GeoTools-Devel mailing list >>>>> GeoTools-Devel@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel >>>>> >>>>
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
