Normally I'd look for the last cite-2.15 to pass but that hasn't run in 8
months. So what is our current practice for release revisions?
Ian
--
Ian Turton
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.ne
I normally check if the last one had successful builds on the build server,
including nightly build, and go for it. If it does not, look for an earlier
one.
Ah mind, I've just merged a security fix related to Spring in GWC and
GeoServer,
it would be great if that was included.
Cheers
Andrea
On T
try them while they are hot -
https://build.geoserver.org/view/geotools/job/geotools-release/
Ian
--
Ian Turton
___
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
Success:
> mvn --version
Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117;
2019-08-27T17:06:16+02:00)
Maven home: /home/aaime/apps/apache-maven-3.6.2
Java version: 1.8.0_242, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: it_IT, platform encoding:
GeoTools / GeoServer PMC meeting - 2020-02-18Attending
Torben Barsballe
Jody Garnett
Andrea Aime
Kevin Smith
Dan Singh
Actions from last meeting
-
N/A
Agenda
-
Build Servers + Website
-
Checkstyle upgrade
-
Release schedule
Actions
-
Torben - reach out t