[Geotools-devel] Build failed in Jenkins: geotools-java11 #233

See Changes: [nuno.oliveira] [GEOT-6179] Fix. Check for client properties on feature chaining. -- [...truncated 982.54 KB...] [INFO] --

[Geotools-devel] Jenkins build is back to normal : geotools-21.x-docs #32

See ___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel

[Geotools-devel] Jenkins build is back to normal : geotools-20.x-docs #44

See ___ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel

Re: [Geotools-devel] GeoTools / GeoServer PMC meeting - 2019-05-28

Hi Andrea Yeah, did notice run.sh expects to be a level higher. I feel like it would make just as much sense to reconfigure run.sh to work from within the cite-tools repo as it would to put it in its own repo (there's already enough repos involved in the cite build as it is), but if you think addi

[Geotools-devel] Build failed in Jenkins: geotools-master-online-mysql #957

See Changes: [nuno.oliveira] [GEOT-6179] Fix. Check for client properties on feature chaining. -- [...truncated 315.56 KB...] Skipping hana tests. Fixture fil

Re: [Geotools-devel] [Geoserver-devel] Automatic GitHub backporting application

That does seem quite useful, and I also agree with Ian that a wider usage of labels on PRs is a good idea. Cheers, Torben On Sun, Jun 2, 2019 at 2:27 AM Ian Turton wrote: > Sounds good to me +1 > > I think we could make more use of labels in general to allow spotting bug > fixes and improvement

[Geotools-devel] Build failed in Jenkins: geotools-master-online-geopackage #930

See Changes: [nuno.oliveira] [GEOT-6179] Fix. Check for client properties on feature chaining. -- [...truncated 288.91 KB...] [ERROR] Te