date:20190917

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11 #1259

2019-09-17 Thread Jenkins

See 



___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-9337) Add Date Created and Date Modified in administration UI lists (layers, styles, ...)

2019-09-17 Thread Imran Rajjad (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
  Imran Rajjad  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-9337  
 
 
  Add Date Created and Date Modified in administration UI lists (layers, styles, ...)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Affects Versions: 
 2.17-RC  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 UI, Wicket UI  
 
 
Created: 
 18/Sep/19 7:32 AM  
 
 
Fix Versions: 
 2.17-RC  
 
 
Priority: 
  Medium  
 
 
Reporter: 
  Imran Rajjad   
 

  
 
 
 
 

 
 In a multiple admin scenario with many layers and styles and a lot of users making changes to layers and styles, there is no direct way of knowing that which elements (e.g Layer or Style) have experienced changes from GUI or REST by other authorized users (e.g Changes in SRS, Default Styles, New Metadata tags and Field types etc), it would be a handy feature for GeoServer admin to glance at the time of creation and modification columns and quickly sort the list as per these columns to review new or modified elements. The system admin should be able to toggle these columns off from system settings, by default it would be disabled. The catalog will need to record the creation and modification time of each object, this could also be configurable from the UI. Link to GSISP: [https://github.com/geosolutions-it/C061-2019-COWI-GS-ENH/wiki/Timestamp-Columns-in-Admin-lists|GSIP 179]

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11-qa #1018

2019-09-17 Thread Jenkins

See 



___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Build failed in Jenkins: geoserver-java11-qa #1017

2019-09-17 Thread Jenkins

See 

--
[...truncated 8.02 KB...]
at java.base/java.lang.Thread.run(Thread.java:834)
jenkins.util.io.CompositeIOException: Unable to remove directory 

 with directory contents: 
[
at 
jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:246)
at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:201)
at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:212)
at 
jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)
at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)
at 
jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)
at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)
at 
jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)
at 
jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:83)
at hudson.Util.deleteContentsRecursive(Util.java:259)
at hudson.Util.deleteContentsRecursive(Util.java:248)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:596)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
java.nio.file.DirectoryNotEmptyException: 

at 
java.base/sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:243)
at 
java.base/sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:110)
at java.base/java.nio.file.Files.deleteIfExists(Files.java:1180)
at 
jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:233)
at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:201)
at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:212)
at 
jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)
at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)
at 
jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)
at jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:211)
at 
jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:222)
at 
jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:83)
at hudson.Util.deleteContentsRecursive(Util.java:259)
at hudson.Util.deleteContentsRecursive(Util.java:248)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:596)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
at hudson.remoting.UserRequest.perform(UserRequest.java:212)
at hudson.remoting.UserRequest.perform(UserRequest.java:54)
at hudson.remoting.Request$2.run(Request.java:369)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
java.nio.file.DirectoryNotEmptyException: 

at 
java.base/sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:243)
at 
java.base/sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:110)
at java.base/java.nio.file.Files.deleteIfExists(Files.java:1180)

[Geoserver-devel] Build failed in Jenkins: geoserver-java11 #1258

2019-09-17 Thread Jenkins

See 

--
[...truncated 1.55 MB...]
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Web Coverage Service 2.0 Earth Observation GUI extension
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Catalog Services for the Web core module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer CAS Security Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer Security Extension Web Modules
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoFence Server
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer REST Api Module-ng
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer Berkley DB Persistence Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Importer Web UI Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping CSW UI Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping GeoServer CAS Security Web Module
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/simple-jndi/simple-jndi/0.11.4.1/simple-jndi-0.11.4.1.pom
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/simple-jndi/simple-jndi/0.11.4.1/simple-jndi-0.11.4.1.pom
 (4.1 kB at 1.4 MB/s)
[INFO] Downloading from boundless: 
https://repo.boundlessgeo.com/main/mysql/mysql-connector-java/5.1.17/mysql-connector-java-5.1.17.jar
[INFO] Downloading from boundless: 
https://repo.boundlessgeo.com/main/simple-jndi/simple-jndi/0.11.4.1/simple-jndi-0.11.4.1.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/mysql/mysql-connector-java/5.1.17/mysql-connector-java-5.1.17.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/simple-jndi/simple-jndi/0.11.4.1/simple-jndi-0.11.4.1.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/mysql/mysql-connector-java/5.1.17/mysql-connector-java-5.1.17.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/simple-jndi/simple-jndi/0.11.4.1/simple-jndi-0.11.4.1.jar
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/mysql/mysql-connector-java/5.1.17/mysql-connector-java-5.1.17.jar
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/simple-jndi/simple-jndi/0.11.4.1/simple-jndi-0.11.4.1.jar
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/simple-jndi/simple-jndi/0.11.4.1/simple-jndi-0.11.4.1.jar
 (43 kB at 8.5 MB/s)
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/mysql/mysql-connector-java/5.1.17/mysql-connector-java-5.1.17.jar
 (788 kB at 49 MB/s)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ gs-sec-jdbc ---
[INFO] 
[INFO] --- git-commit-id-plugin:2.1.15:revision (default) @ gs-sec-jdbc ---
[INFO] 
[INFO] ---

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11 #1257

2019-09-17 Thread Jenkins

See 



___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Build failed in Jenkins: geoserver-java11 #1256

2019-09-17 Thread Jenkins

See 

--
[...truncated 1.34 MB...]
[INFO] Downloading from boundless: 
https://repo.boundlessgeo.com/main/opendap/opendap/2.1/opendap-2.1.jar
[INFO] Downloading from boundless: 
https://repo.boundlessgeo.com/main/commons-cli/commons-cli/1.4/commons-cli-1.4.jar
[INFO] Downloaded from boundless: 
https://repo.boundlessgeo.com/main/edu/ucar/netcdf4/4.6.11/netcdf4-4.6.11.jar 
(60 kB at 102 kB/s)
[INFO] Downloading from boundless: 
https://repo.boundlessgeo.com/main/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar
[INFO] Downloaded from boundless: 
https://repo.boundlessgeo.com/main/opendap/opendap/2.1/opendap-2.1.jar (441 kB 
at 748 kB/s)
[INFO] Downloading from boundless: 
https://repo.boundlessgeo.com/main/org/geotools/gt-sample-data/23-SNAPSHOT/gt-sample-data-23-20190917.221747-17.jar
[INFO] Downloaded from boundless: 
https://repo.boundlessgeo.com/main/edu/ucar/bufr/4.6.11/bufr-4.6.11.jar (2.5 MB 
at 4.1 MB/s)
[INFO] Downloaded from boundless: 
https://repo.boundlessgeo.com/main/org/geotools/gt-sample-data/23-SNAPSHOT/gt-sample-data-23-20190917.221747-17.jar
 (4.0 MB at 5.9 MB/s)
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/org/apache/httpcomponents/httpmime/4.5.1/httpmime-4.5.1.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/org/quartz-scheduler/quartz/2.2.0/quartz-2.2.0.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/c3p0/c3p0/0.9.1.1/c3p0-0.9.1.1.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/com/google/protobuf/protobuf-java/3.5.0/protobuf-java-3.5.0.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/com/beust/jcommander/1.35/jcommander-1.35.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/com/amazonaws/aws-java-sdk-s3/1.11.236/aws-java-sdk-s3-1.11.236.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/com/amazonaws/aws-java-sdk-kms/1.11.236/aws-java-sdk-kms-1.11.236.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/com/amazonaws/aws-java-sdk-core/1.11.236/aws-java-sdk-core-1.11.236.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/software/amazon/ion/ion-java/1.0.2/ion-java-1.0.2.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/com/fasterxml/jackson/dataformat/jackson-dataformat-cbor/2.6.7/jackson-dataformat-cbor-2.6.7.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/com/amazonaws/jmespath-java/1.11.236/jmespath-java-1.11.236.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/org/jsoup/jsoup/1.10.2/jsoup-1.10.2.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/commons-cli/commons-cli/1.4/commons-cli-1.4.jar
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/httpcomponents/httpmime/4.5.1/httpmime-4.5.1.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/quartz-scheduler/quartz/2.2.0/quartz-2.2.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/c3p0/c3p0/0.9.1.1/c3p0-0.9.1.1.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/google/protobuf/protobuf-java/3.5.0/protobuf-java-3.5.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/beust/jcommander/1.35/jcommander-1.35.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/amazonaws/aws-java-sdk-s3/1.11.236/aws-java-sdk-s3-1.11.236.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/amazonaws/aws-java-sdk-kms/1.11.236/aws-java-sdk-kms-1.11.236.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/amazonaws/aws-java-sdk-core/1.11.236/aws-java-sdk-core-1.11.236.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/software/amazon/ion/ion-java/1.0.2/ion-java-1.0.2.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/fasterxml/jackson/dataformat/jackson-dataformat-cbor/2.6.7/jackson-dataformat-cbor-2.6.7.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/amazonaws/jmespath-java/1.11.236/jmespath-java-1.11.236.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/jsoup/jsoup/1.10.2/jsoup-1.10.2.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/commons-cli/commons-cli/1.4/commons-cli-1.4.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/slf4j/log4j-over-slf4j/1.6.4/log4j-over-slf4j-1.6.4.jar
[INFO] Downloading from central:

Re: [Geoserver-devel] GSIP-176

2019-09-17 Thread Jody Garnett

I added one sentence to separate out "running the tests" from "formal
certification", and added a graph to show current funding progress.
Please check and publish when ready. I don't want to hit publish myself on
the off chance it shows up as published in my name, and I think this will
have more impact coming from you :)
--
Jody Garnett


On Tue, 17 Sep 2019 at 14:34, Ilya Rosenfeld 
wrote:

> Jody - I’ve updated the copy to take emphasis off “reference
> implementation” aspect of the message. Please let me know if the updated
> version suits.
>
> Also curious- assuming that this initiative succeeded, what impediment is
> there to host a reference implementation server? - Ilya
>
>
> Sent from my iPhone
>
> On Sep 17, 2019, at 12:19 PM, Jody Garnett  wrote:
>
> Checking now.
>
> I think we may need a stronger opening, the first sentence is not true:
>
> | GeoServer has long been a reference implementation of core OGC
> Standards: WMS, WFS, and WCS.
>
> Although GeoServer appears on the wiki page we do not qualify as a
> reference implementation: a) we have not submitted cite test results b) we
> do not provide a hosted geoserver for the public to test against
>
> Ideas for a first sentence:
>
> *Does your organization use OGC protocols to meet interoperability and
> regulatory requirements? GeoServer build infrastructure needs your help to
> ensure our project can continue to meet your needs.*
>
> Background:
>
> - Our website shows "built on standards" listing "certified ogc
> compliant", if we wish to keep these stickers we will need to pass the CITE
> tests. As an example GeoServer was last certified by OpenGeo in 2004, and
> Boundless in 2012.
>
> - Although GeoServer was considered a reference implementation that is no
> longer the case. OSGeo has offered to provide hosting of a running service
> if we wish to be recognized as a reference implementation again.
>
> --
> Jody Garnett
>
>
> On Tue, 17 Sep 2019 at 06:43, Ilya Rosenfeld 
> wrote:
>
>> Thanks Jody.. duly noted.
>>
>> Here’s the blog post draft:
>> http://blog.geoserver.org/?p=3055=true
>>
>> Please feel free to chime in / throw stones. Not sure who hits “publish”
>> but the content is complete on my end.
>>
>> Cheers,
>> Ilya
>>
>>
>>
>>
>> Sent from my iPhone
>>
>> On Sep 16, 2019, at 2:43 PM, Jody Garnett  wrote:
>>
>> I set a couple targets on the GSIP-176, however they are only a
>> wild-guess (as we would still need anyone to respond to an RFP call).
>>
>> I have updated the GSIP page to make the target/progress more clear:
>>
>> - baseline: 5000 budget from osgeo
>> - target 1: 1 funding raising
>> - target 2: 15000 funding target
>>
>> Basically if we do not meet the first target 1 I do not think the PSC
>> should bother issuing an RFP. By the same token if we get a bunch of
>> proposals in outside of our range we may not proceed.
>>
>> I had several chats on this subject at foss4g many groups were hopeful of
>> skipping cite compatibility for WFS/WMS/WCS/WPS and wanting to focus on
>> openapi. While I like the enthusiasm it will be some time yet before those
>> standards are ready, and even when they are we would like to keep
>> supporting WFS/WFS/WCS/WPS.
>> --
>> Jody Garnett
>>
>>
>> On Mon, 16 Sep 2019 at 06:37, Ilya Rosenfeld 
>> wrote:
>>
>>> Thanks, Jody. I’m curious, under ideal circumstances, what budget is
>>> required to get it fully under control and implemented? In other words if
>>> we were to set a fundraising target, what would be a solid number?
>>>
>>>
>>> Sent from my iPhone
>>>
>>> On Sep 15, 2019, at 10:32 PM, Jody Garnett 
>>> wrote:
>>>
>>> Thanks for your hustle on this Ilya, adding you the blog.geoserver.org
>>> now.
>>>
>>> While we did mention this challenge during the state of geoserver
>>> presentation we did not linger on the fundraising aspect.
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Sun, 15 Sep 2019 at 12:09, Ilya Rosenfeld 
>>> wrote:
>>>
 Greetings -

 As some of you probably know, I took it upon myself to raise awareness
 and try to drum up some funding for the CITE testing automation initiative
 on LinkedIn
 .
 It was gratifying to see all the positive response expressed in Likes and
 re-shares, but unfortunately that didn't produce much funding. (Other than
 my own, I think there was only one more contribution made via PayPal that
 was set up specifically for this.) So perhaps a subsequent tactic to keep
 the ball rolling is to leverage the first wave of response, publish a guest
 blog post on GeoServer site (per Jody's idea) and socialize via Twitter.
 I'm happy to adapt the original post if need-be and provide content for the
 blog.

 BTW going forward, I'm also happy to help managing this initiative to
 completion. I sincerely believe it's a very important one and certainly
 have the quals to help.

 Cheers
 Ilya

Re: [Geoserver-devel] GSIP-176

2019-09-17 Thread Jody Garnett

I have thought a bit about hosting a reference implementation, if we just
host the server in read-only mode - all that is needed is a machine (which
OSGeo has offered to provide). If we host WFS-T (say to pass CITE tests) we
would also need the ability to reset the dataset after a test run. I was
thinking we could make a demo page for "cite" that could reload the data,
or a rest api endpoint.

But yeah the key impediment is someone to provide hardware, even with
OSGeo's offer we then need someone to setup the machine.

It has been really kind of first boundless and now GeoSolutions to provide
a machine for the base maps shown on the geoserver.org website.
--
Jody Garnett


On Tue, 17 Sep 2019 at 14:34, Ilya Rosenfeld 
wrote:

> Jody - I’ve updated the copy to take emphasis off “reference
> implementation” aspect of the message. Please let me know if the updated
> version suits.
>
> Also curious- assuming that this initiative succeeded, what impediment is
> there to host a reference implementation server? - Ilya
>
>
> Sent from my iPhone
>
> On Sep 17, 2019, at 12:19 PM, Jody Garnett  wrote:
>
> Checking now.
>
> I think we may need a stronger opening, the first sentence is not true:
>
> | GeoServer has long been a reference implementation of core OGC
> Standards: WMS, WFS, and WCS.
>
> Although GeoServer appears on the wiki page we do not qualify as a
> reference implementation: a) we have not submitted cite test results b) we
> do not provide a hosted geoserver for the public to test against
>
> Ideas for a first sentence:
>
> *Does your organization use OGC protocols to meet interoperability and
> regulatory requirements? GeoServer build infrastructure needs your help to
> ensure our project can continue to meet your needs.*
>
> Background:
>
> - Our website shows "built on standards" listing "certified ogc
> compliant", if we wish to keep these stickers we will need to pass the CITE
> tests. As an example GeoServer was last certified by OpenGeo in 2004, and
> Boundless in 2012.
>
> - Although GeoServer was considered a reference implementation that is no
> longer the case. OSGeo has offered to provide hosting of a running service
> if we wish to be recognized as a reference implementation again.
>
> --
> Jody Garnett
>
>
> On Tue, 17 Sep 2019 at 06:43, Ilya Rosenfeld 
> wrote:
>
>> Thanks Jody.. duly noted.
>>
>> Here’s the blog post draft:
>> http://blog.geoserver.org/?p=3055=true
>>
>> Please feel free to chime in / throw stones. Not sure who hits “publish”
>> but the content is complete on my end.
>>
>> Cheers,
>> Ilya
>>
>>
>>
>>
>> Sent from my iPhone
>>
>> On Sep 16, 2019, at 2:43 PM, Jody Garnett  wrote:
>>
>> I set a couple targets on the GSIP-176, however they are only a
>> wild-guess (as we would still need anyone to respond to an RFP call).
>>
>> I have updated the GSIP page to make the target/progress more clear:
>>
>> - baseline: 5000 budget from osgeo
>> - target 1: 1 funding raising
>> - target 2: 15000 funding target
>>
>> Basically if we do not meet the first target 1 I do not think the PSC
>> should bother issuing an RFP. By the same token if we get a bunch of
>> proposals in outside of our range we may not proceed.
>>
>> I had several chats on this subject at foss4g many groups were hopeful of
>> skipping cite compatibility for WFS/WMS/WCS/WPS and wanting to focus on
>> openapi. While I like the enthusiasm it will be some time yet before those
>> standards are ready, and even when they are we would like to keep
>> supporting WFS/WFS/WCS/WPS.
>> --
>> Jody Garnett
>>
>>
>> On Mon, 16 Sep 2019 at 06:37, Ilya Rosenfeld 
>> wrote:
>>
>>> Thanks, Jody. I’m curious, under ideal circumstances, what budget is
>>> required to get it fully under control and implemented? In other words if
>>> we were to set a fundraising target, what would be a solid number?
>>>
>>>
>>> Sent from my iPhone
>>>
>>> On Sep 15, 2019, at 10:32 PM, Jody Garnett 
>>> wrote:
>>>
>>> Thanks for your hustle on this Ilya, adding you the blog.geoserver.org
>>> now.
>>>
>>> While we did mention this challenge during the state of geoserver
>>> presentation we did not linger on the fundraising aspect.
>>> --
>>> Jody Garnett
>>>
>>>
>>> On Sun, 15 Sep 2019 at 12:09, Ilya Rosenfeld 
>>> wrote:
>>>
 Greetings -

 As some of you probably know, I took it upon myself to raise awareness
 and try to drum up some funding for the CITE testing automation initiative
 on LinkedIn
 .
 It was gratifying to see all the positive response expressed in Likes and
 re-shares, but unfortunately that didn't produce much funding. (Other than
 my own, I think there was only one more contribution made via PayPal that
 was set up specifically for this.) So perhaps a subsequent tactic to keep
 the ball rolling is to leverage the first wave of response, publish a guest
 blog post on GeoServer site (per

Re: [Geoserver-devel] GSIP-176

2019-09-17 Thread Ilya Rosenfeld

Jody - I’ve updated the copy to take emphasis off “reference implementation” 
aspect of the message. Please let me know if the updated version suits. 

Also curious- assuming that this initiative succeeded, what impediment is there 
to host a reference implementation server? - Ilya 


Sent from my iPhone

> On Sep 17, 2019, at 12:19 PM, Jody Garnett  wrote:
> 
> Checking now.
> 
> I think we may need a stronger opening, the first sentence is not true:
> 
> | GeoServer has long been a reference implementation of core OGC Standards: 
> WMS, WFS, and WCS. 
> 
> Although GeoServer appears on the wiki page we do not qualify as a reference 
> implementation: a) we have not submitted cite test results b) we do not 
> provide a hosted geoserver for the public to test against
> 
> Ideas for a first sentence:
> 
> Does your organization use OGC protocols to meet interoperability and 
> regulatory requirements? GeoServer build infrastructure needs your help to 
> ensure our project can continue to meet your needs.
> 
> Background:
> 
> - Our website shows "built on standards" listing "certified ogc compliant", 
> if we wish to keep these stickers we will need to pass the CITE tests. As an 
> example GeoServer was last certified by OpenGeo in 2004, and Boundless in 
> 2012.
> 
> - Although GeoServer was considered a reference implementation that is no 
> longer the case. OSGeo has offered to provide hosting of a running service if 
> we wish to be recognized as a reference implementation again.
> 
> --
> Jody Garnett
> 
> 
>> On Tue, 17 Sep 2019 at 06:43, Ilya Rosenfeld  
>> wrote:
>> Thanks Jody.. duly noted.
>> 
>> Here’s the blog post draft: http://blog.geoserver.org/?p=3055=true
>> 
>> Please feel free to chime in / throw stones. Not sure who hits “publish” but 
>> the content is complete on my end.
>> 
>> Cheers,
>> Ilya
>> 
>> 
>> 
>> 
>> Sent from my iPhone
>> 
>>> On Sep 16, 2019, at 2:43 PM, Jody Garnett  wrote:
>>> 
>>> I set a couple targets on the GSIP-176, however they are only a wild-guess 
>>> (as we would still need anyone to respond to an RFP call).
>>> 
>>> I have updated the GSIP page to make the target/progress more clear:
>>> 
>>> - baseline: 5000 budget from osgeo
>>> - target 1: 1 funding raising
>>> - target 2: 15000 funding target 
>>> 
>>> Basically if we do not meet the first target 1 I do not think the PSC 
>>> should bother issuing an RFP. By the same token if we get a bunch of 
>>> proposals in outside of our range we may not proceed.
>>> 
>>> I had several chats on this subject at foss4g many groups were hopeful of 
>>> skipping cite compatibility for WFS/WMS/WCS/WPS and wanting to focus on 
>>> openapi. While I like the enthusiasm it will be some time yet before those 
>>> standards are ready, and even when they are we would like to keep 
>>> supporting WFS/WFS/WCS/WPS.
>>> --
>>> Jody Garnett
>>> 
>>> 
 On Mon, 16 Sep 2019 at 06:37, Ilya Rosenfeld  
 wrote:
 Thanks, Jody. I’m curious, under ideal circumstances, what budget is 
 required to get it fully under control and implemented? In other words if 
 we were to set a fundraising target, what would be a solid number? 
 
 
 Sent from my iPhone
 
> On Sep 15, 2019, at 10:32 PM, Jody Garnett  wrote:
> 
> Thanks for your hustle on this Ilya, adding you the blog.geoserver.org 
> now.
> 
> While we did mention this challenge during the state of geoserver 
> presentation we did not linger on the fundraising aspect.
> --
> Jody Garnett
> 
> 
>> On Sun, 15 Sep 2019 at 12:09, Ilya Rosenfeld 
>>  wrote:
>> Greetings - 
>> 
>> As some of you probably know, I took it upon myself to raise awareness 
>> and try to drum up some funding for the CITE testing automation 
>> initiative on LinkedIn. It was gratifying to see all the positive 
>> response expressed in Likes and re-shares, but unfortunately that didn't 
>> produce much funding. (Other than my own, I think there was only one 
>> more contribution made via PayPal that was set up specifically for 
>> this.) So perhaps a subsequent tactic to keep the ball rolling is to 
>> leverage the first wave of response, publish a guest blog post on 
>> GeoServer site (per Jody's idea) and socialize via Twitter. I'm happy to 
>> adapt the original post if need-be and provide content for the blog.
>> 
>> BTW going forward, I'm also happy to help managing this initiative to 
>> completion. I sincerely believe it's a very important one and certainly 
>> have the quals to help.
>> 
>> Cheers
>> Ilya Rosenfeld
>> 
>> 
>> 
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11-qa #1011

2019-09-17 Thread Jenkins

See 



___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Build failed in Jenkins: geoserver-java11-qa #1010

2019-09-17 Thread Jenkins

See 

--
[...truncated 979.64 KB...]
[INFO] Downloading from osgeo: 
http://download.osgeo.org/webdav/geotools/org/apache/httpcomponents/httpclient-cache/4.5.5/httpclient-cache-4.5.5.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-transcoder/1.10/batik-transcoder-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-anim/1.10/batik-anim-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-css/1.10/batik-css-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-ext/1.10/batik-ext-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-parser/1.10/batik-parser-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-svg-dom/1.10/batik-svg-dom-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-awt-util/1.10/batik-awt-util-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/xmlgraphics-commons/2.2/xmlgraphics-commons-2.2.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-bridge/1.10/batik-bridge-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-script/1.10/batik-script-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-dom/1.10/batik-dom-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-gvt/1.10/batik-gvt-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-svggen/1.10/batik-svggen-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-util/1.10/batik-util-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-constants/1.10/batik-constants-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-i18n/1.10/batik-i18n-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/xmlgraphics/batik-xml/1.10/batik-xml-1.10.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/xml-apis/xml-apis-ext/1.3.04/xml-apis-ext-1.3.04.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/lowagie/itext/2.1.5/itext-2.1.5.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/ar/com/hjg/pngj/2.0.1/pngj-2.0.1.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/xalan/xalan/2.7.2/xalan-2.7.2.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/xalan/serializer/2.7.2/serializer-2.7.2.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/xml-apis/xml-apis/1.4.01/xml-apis-1.4.01.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/springframework/spring-context-support/5.1.1.RELEASE/spring-context-support-5.1.1.RELEASE.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/mockito/mockito-core/2.23.0/mockito-core-2.23.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/net/bytebuddy/byte-buddy/1.9.0/byte-buddy-1.9.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/net/bytebuddy/byte-buddy-agent/1.9.0/byte-buddy-agent-1.9.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/pdfbox/pdfbox/2.0.12/pdfbox-2.0.12.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/pdfbox/fontbox/2.0.12/fontbox-2.0.12.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/jaitools/jt-rangelookup/1.5.0/jt-rangelookup-1.5.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/jaitools/jt-contour/1.5.0/jt-contour-1.5.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/jaitools/jt-attributeop/1.5.0/jt-attributeop-1.5.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/jaitools/jt-vectorize/1.5.0/jt-vectorize-1.5.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/antlr/antlr4-runtime/4.7.1/antlr4-runtime-4.7.1.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/codehaus/janino/janino/3.0.8/janino-3.0.8.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/codehaus/janino/commons-compiler/3.0.8/commons-compiler-3.0.8.jar
[INFO] Downloading from geosolutions:

[Geoserver-devel] GeoTools / GeoServer PMC meeting - 2019-09-17

2019-09-17 Thread Torben Barsballe via Geoserver-devel

Attending

Torben Barsballe

Kevin Smith

Andrea Aime

Alessandro Parma

Jukka Rahkonen

Jan Boonen

Josh Fix
Actions from last meeting

[DONE] Jody: Draft AGM Update for GeoTools & GeoServer. Ian/Torben to
review
-

2.15.3 Release in limbo -> AA will do it after 2.16.0 - Thanks!

Agenda

PSC Update
2.

GeoServer Docker Images
3.

GeoTools COG Datastore
4.

2.16.0 Release
5.

GSIP-176 Cite Test Activity

Actions

(done) agm-meeting slides

for geotools and geoserver

PSC Update

Brad has stepped, thanks for your service.

Discussion on PSC representation:

Desire for more user representation, do not see any active users to
nominate :(
-

Nuno is an active developer
-

discussion of balance, with so many GeoSolutions active we can get a
lot of +0/-0 in case a proposal is coming from GeoSolutions itself

GeoServer Docker Container

Some requests last year, follow up to foss4g discussion:

Request on geoserver devel about this earlier in 2019
-

Kartoza docker image very popular and is often the key way developers
access

List of images:

https://hub.docker.com/r/kartoza/geoserver/
-

vector tiles, control-flow, monitoring, ...

https://hub.docker.com/r/boonen/geoserver
-

vector tiles, csw, control flow, jpegturbo, jdbcconfig, gdal, excel,
charts
-

https://hub.docker.com/r/geosolutionsit/geoserver
-

monitor, status monitoring, control flow, jpegTurbo, ...

Q: Discussion on how to handle extensions:

Option: environment variables to control installing of extension
-

see setup.sh

example to download at build time
-

discussion: could download build time, and install at run time
-

Option: tagged builds with different profiles
-

consider minimal, …

Q: Data directory - how to handle?

Use of default or minimal default
-

JDBCConfig + JDBCStore (this is very much a community module) → Jan is
thinking to start working on these modules
-

Option: transient inside container
-

Option: externalize file system, data directory, tilecache etc..

Q: Scope

Developer plaything for testing? Like windows installer :) (that is
still often used for production…)
-

Production image? Seems the case from control-flow, monitoring, …
-

Aside: discussion on control-flow configuration settings
-

Aside: discussion of PostGIS container automatically configuring,
see: https://pgtune.leopard.in.ua/#/
-

Security scan is possible with some image repositories, e.g.

Configuration options:

Ubuntu baseline
-

JNDI - one has optional JNDI for PostGIS (

https://github.com/boonen/docker-geoserver/blob/master/assets/confd/templates/context.xml.tmpl#L35
)
-

CORS - or reverse proxy in front of GeoServer or
https://github.com/kartoza/docker-geoserver#build-with-cors-support
-

Tomcat Version
-

Java Version: Did a test and it worked quite well to support multiple
java versions

How to start this?

Repository
1.

Start at github.com/geoserver/docker ← (done) jody to setup
repository and team
2.

Start at hub.docker.com/u/geoserver/geoserver ← contains prebuilt
images
1.

Needs to set up organization
2.

Approach
1.

Start from scratch?
2.

Start from one that is close …
3.

Release process?
1.

Start off manually
2.

We really want this done at build.geoserver.org at the end of the day
3.

Is it just an environment variable? To download latest versions…
4.

Nightly build? “nightly-master” “nightly-stable” “nightly-maintenance”
Version: “2.14-nightly”, ..
5.

Development stream: “stable” ,”maintenance”
6.

Release series: “2.15”, “2.14”, …

COG reader

Pure java implementation, doing range requests, caching optional, more info
here:

https://github.com/joshfix/cog-image-reader

Base class extending imageio-ext TiffImageReader

A couple classes are copied wholesale with a few modifications due to
visibility restrictions (private / final) in the code

Is this going to be a problem with license? - ImageIO-ext is LGPLv3,
ImageIO is (mostly) BSD.
-

Can we just modify the classes in question to relax these restrictions -
yes, as long as it is in imageio-ext

Configuration

Can mostly be done via coverage parameters in GT/GS
-

How to configure caching parameters?
-

Environment variables for now, to get this moving along
-

COG Reader SPI

Make two

Re: [Geoserver-devel] Joining the GeoServer meeting?

2019-09-17 Thread Andrea Aime

Hi Tim,
the day did not change, it's today (well, in 5 minutes :-D)

Cheers
Andrea


On Tue, Sep 17, 2019 at 3:13 PM Tim Sutton  wrote:

> Hi
>
> Yes I will be there today (17th) or did the date change?
>
> Regards
>
> Tim
>
> On 17 Sep 2019, at 03:54, Jody Garnett  wrote:
>
> Torben has sent out the reminder, I hope you both can attend tomorrow.
> --
> Jody Garnett
>
>
> On Wed, 4 Sep 2019 at 00:17, Tim Sutton  wrote:
>
>> Hi
>>
>> Cool - Jan has contacted me off list too. I will try to join the call too
>> - along with Admire who actually does all the hard work maintaining our
>> GeoServer docker image.
>>
>> Regards
>>
>> Tim
>>
>> On 4 Sep 2019, at 05:46, Jody Garnett  wrote:
>>
>> Thanks Jan, Tim Sutton (CCed) also expressed an interest in this activity.
>>
>> Our next meeting is in two weeks (Sep 17) the meeting details are:
>>
>> Jitsi: https://meet.jit.si/GeoServerMeeting
>> 
>> Meeting time: 16:30 UTC
>> 
>>
>>
>> Ideally
>> we send a meeting reminder to this list before hand.
>> --
>> Jody Garnett
>>
>>
>> On Tue, 3 Sep 2019 at 09:37, Jan Boonen  wrote:
>>
>>> Hi everyone,
>>>
>>> This FOSS4G I tried to contribute to GeoTools and GeoServer for the
>>> first time during the code sprint and it was fun. One of the results was an
>>> interesting chat with Jody on creating an official Docker image of
>>> GeoServer. I'm very happy to contribute on this and have
>>>
>>> If possible I'd like to talk with you about this during the bi-weekly
>>> GeoServer meeting. Could somebody let me know when the meeting takes place
>>> and how I can join the meeting?
>>>
>>> Kind regards,
>>>
>>> Jan
>>>
>>> --
>>> Geodan
>>> Buitenhaven 27-A
>>> 5211 TP 's-Hertogenbosch (NL)
>>>
>>> T +31 (0)73 - 692 5151
>>> M +31 (0)6 - 2395 1191
>>> E jan.boo...@geodan.nl
>>> www.geodan.nl | disclaimer 
>>> --
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>> —
>>
>>
>> 
>>
>>
>>
>>
>>
>>
>> *Tim Sutton*
>>
>> *Co-founder:* Kartoza
>> *Ex Project chair:* QGIS.org 
>>
>> Visit http://kartoza.com to find out about open source:
>>
>> Desktop GIS programming services
>> Geospatial web development
>> GIS Training
>> Consulting Services
>>
>> *Skype*: timlinux
>> *IRC:* timlinux on #qgis at freenode.net
>>
>> I'd love to connect. Here's my calendar link
>>  to make finding time easy.
>>
>>
> —
>
>
>
>
>
>
>
>
> *Tim Sutton*
>
> *Co-founder:* Kartoza
> *Ex Project chair:* QGIS.org
>
> Visit http://kartoza.com to find out about open source:
>
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
>
> *Skype*: timlinux
> *IRC:* timlinux on #qgis at freenode.net
>
> I'd love to connect. Here's my calendar link
>  to make finding time easy.
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 

Regards, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054
Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it
--- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European

Re: [Geoserver-devel] GSIP-176

2019-09-17 Thread Jody Garnett

Checking now.

I think we may need a stronger opening, the first sentence is not true:

| GeoServer has long been a reference implementation of core OGC Standards:
WMS, WFS, and WCS.

Although GeoServer appears on the wiki page we do not qualify as a
reference implementation: a) we have not submitted cite test results b) we
do not provide a hosted geoserver for the public to test against

Ideas for a first sentence:

*Does your organization use OGC protocols to meet interoperability and
regulatory requirements? GeoServer build infrastructure needs your help to
ensure our project can continue to meet your needs.*

Background:

- Our website shows "built on standards" listing "certified ogc compliant",
if we wish to keep these stickers we will need to pass the CITE tests. As
an example GeoServer was last certified by OpenGeo in 2004, and Boundless
in 2012.

- Although GeoServer was considered a reference implementation that is no
longer the case. OSGeo has offered to provide hosting of a running service
if we wish to be recognized as a reference implementation again.

--
Jody Garnett


On Tue, 17 Sep 2019 at 06:43, Ilya Rosenfeld 
wrote:

> Thanks Jody.. duly noted.
>
> Here’s the blog post draft: http://blog.geoserver.org/?p=3055=true
>
> Please feel free to chime in / throw stones. Not sure who hits “publish”
> but the content is complete on my end.
>
> Cheers,
> Ilya
>
>
>
>
> Sent from my iPhone
>
> On Sep 16, 2019, at 2:43 PM, Jody Garnett  wrote:
>
> I set a couple targets on the GSIP-176, however they are only a wild-guess
> (as we would still need anyone to respond to an RFP call).
>
> I have updated the GSIP page to make the target/progress more clear:
>
> - baseline: 5000 budget from osgeo
> - target 1: 1 funding raising
> - target 2: 15000 funding target
>
> Basically if we do not meet the first target 1 I do not think the PSC
> should bother issuing an RFP. By the same token if we get a bunch of
> proposals in outside of our range we may not proceed.
>
> I had several chats on this subject at foss4g many groups were hopeful of
> skipping cite compatibility for WFS/WMS/WCS/WPS and wanting to focus on
> openapi. While I like the enthusiasm it will be some time yet before those
> standards are ready, and even when they are we would like to keep
> supporting WFS/WFS/WCS/WPS.
> --
> Jody Garnett
>
>
> On Mon, 16 Sep 2019 at 06:37, Ilya Rosenfeld 
> wrote:
>
>> Thanks, Jody. I’m curious, under ideal circumstances, what budget is
>> required to get it fully under control and implemented? In other words if
>> we were to set a fundraising target, what would be a solid number?
>>
>>
>> Sent from my iPhone
>>
>> On Sep 15, 2019, at 10:32 PM, Jody Garnett 
>> wrote:
>>
>> Thanks for your hustle on this Ilya, adding you the blog.geoserver.org
>> now.
>>
>> While we did mention this challenge during the state of geoserver
>> presentation we did not linger on the fundraising aspect.
>> --
>> Jody Garnett
>>
>>
>> On Sun, 15 Sep 2019 at 12:09, Ilya Rosenfeld 
>> wrote:
>>
>>> Greetings -
>>>
>>> As some of you probably know, I took it upon myself to raise awareness
>>> and try to drum up some funding for the CITE testing automation initiative
>>> on LinkedIn
>>> .
>>> It was gratifying to see all the positive response expressed in Likes and
>>> re-shares, but unfortunately that didn't produce much funding. (Other than
>>> my own, I think there was only one more contribution made via PayPal that
>>> was set up specifically for this.) So perhaps a subsequent tactic to keep
>>> the ball rolling is to leverage the first wave of response, publish a guest
>>> blog post on GeoServer site (per Jody's idea) and socialize via Twitter.
>>> I'm happy to adapt the original post if need-be and provide content for the
>>> blog.
>>>
>>> BTW going forward, I'm also happy to help managing this initiative to
>>> completion. I sincerely believe it's a very important one and certainly
>>> have the quals to help.
>>>
>>> Cheers
>>> Ilya Rosenfeld
>>>
>>>
>>>
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Jenkins build is back to normal : geoserver-2.15.x-java11 #216

2019-09-17 Thread Jenkins

See 




___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP-176

2019-09-17 Thread Ilya Rosenfeld

Thanks Jody.. duly noted.

Here’s the blog post draft: http://blog.geoserver.org/?p=3055=true

Please feel free to chime in / throw stones. Not sure who hits “publish” but 
the content is complete on my end.

Cheers,
Ilya

Sent from my iPhone

> On Sep 16, 2019, at 2:43 PM, Jody Garnett  wrote:
> 
> I set a couple targets on the GSIP-176, however they are only a wild-guess 
> (as we would still need anyone to respond to an RFP call).
> 
> I have updated the GSIP page to make the target/progress more clear:
> 
> - baseline: 5000 budget from osgeo
> - target 1: 1 funding raising
> - target 2: 15000 funding target 
> 
> Basically if we do not meet the first target 1 I do not think the PSC should 
> bother issuing an RFP. By the same token if we get a bunch of proposals in 
> outside of our range we may not proceed.
> 
> I had several chats on this subject at foss4g many groups were hopeful of 
> skipping cite compatibility for WFS/WMS/WCS/WPS and wanting to focus on 
> openapi. While I like the enthusiasm it will be some time yet before those 
> standards are ready, and even when they are we would like to keep supporting 
> WFS/WFS/WCS/WPS.
> --
> Jody Garnett
> 
> 
>> On Mon, 16 Sep 2019 at 06:37, Ilya Rosenfeld  
>> wrote:
>> Thanks, Jody. I’m curious, under ideal circumstances, what budget is 
>> required to get it fully under control and implemented? In other words if we 
>> were to set a fundraising target, what would be a solid number? 
>> 
>> 
>> Sent from my iPhone
>> 
>>> On Sep 15, 2019, at 10:32 PM, Jody Garnett  wrote:
>>> 
>>> Thanks for your hustle on this Ilya, adding you the blog.geoserver.org now.
>>> 
>>> While we did mention this challenge during the state of geoserver 
>>> presentation we did not linger on the fundraising aspect.
>>> --
>>> Jody Garnett
>>> 
>>> 
 On Sun, 15 Sep 2019 at 12:09, Ilya Rosenfeld  
 wrote:
 Greetings - 

 As some of you probably know, I took it upon myself to raise awareness and 
 try to drum up some funding for the CITE testing automation initiative on 
 LinkedIn. It was gratifying to see all the positive response expressed in 
 Likes and re-shares, but unfortunately that didn't produce much funding. 
 (Other than my own, I think there was only one more contribution made via 
 PayPal that was set up specifically for this.) So perhaps a subsequent 
 tactic to keep the ball rolling is to leverage the first wave of response, 
 publish a guest blog post on GeoServer site (per Jody's idea) and 
 socialize via Twitter. I'm happy to adapt the original post if need-be and 
 provide content for the blog.

 BTW going forward, I'm also happy to help managing this initiative to 
 completion. I sincerely believe it's a very important one and certainly 
 have the quals to help.

 Cheers
 Ilya Rosenfeld

 ___
 Geoserver-devel mailing list
 Geoserver-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geoserver-devel
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Joining the GeoServer meeting?

2019-09-17 Thread Jan Boonen

Hi all,

I will attend the meeting. In the meantime I have migrated our company
Docker image to a public Github repository:
https://github.com/boonen/docker-geoserver. Images can be downloaded and
tested from https://hub.docker.com/r/boonen/geoserver.

Cheers,

Jan

--
Geodan
Buitenhaven 27-A
5211 TP 's-Hertogenbosch (NL)

T +31 (0)73 - 692 5151
M +31 (0)6 - 2395 1191
E jan.boo...@geodan.nl
www.geodan.nl | disclaimer 
--


Op di 17 sep. 2019 om 04:55 schreef Jody Garnett :

> Torben has sent out the reminder, I hope you both can attend tomorrow.
> --
> Jody Garnett
>
>
> On Wed, 4 Sep 2019 at 00:17, Tim Sutton  wrote:
>
>> Hi
>>
>> Cool - Jan has contacted me off list too. I will try to join the call too
>> - along with Admire who actually does all the hard work maintaining our
>> GeoServer docker image.
>>
>> Regards
>>
>> Tim
>>
>> On 4 Sep 2019, at 05:46, Jody Garnett  wrote:
>>
>> Thanks Jan, Tim Sutton (CCed) also expressed an interest in this activity.
>>
>> Our next meeting is in two weeks (Sep 17) the meeting details are:
>>
>> Jitsi: https://meet.jit.si/GeoServerMeeting
>> 
>> Meeting time: 16:30 UTC
>> 
>>
>>
>> Ideally
>> we send a meeting reminder to this list before hand.
>> --
>> Jody Garnett
>>
>>
>> On Tue, 3 Sep 2019 at 09:37, Jan Boonen  wrote:
>>
>>> Hi everyone,
>>>
>>> This FOSS4G I tried to contribute to GeoTools and GeoServer for the
>>> first time during the code sprint and it was fun. One of the results was an
>>> interesting chat with Jody on creating an official Docker image of
>>> GeoServer. I'm very happy to contribute on this and have
>>>
>>> If possible I'd like to talk with you about this during the bi-weekly
>>> GeoServer meeting. Could somebody let me know when the meeting takes place
>>> and how I can join the meeting?
>>>
>>> Kind regards,
>>>
>>> Jan
>>>
>>> --
>>> Geodan
>>> Buitenhaven 27-A
>>> 5211 TP 's-Hertogenbosch (NL)
>>>
>>> T +31 (0)73 - 692 5151
>>> M +31 (0)6 - 2395 1191
>>> E jan.boo...@geodan.nl
>>> www.geodan.nl | disclaimer 
>>> --
>>> ___
>>> Geoserver-devel mailing list
>>> Geoserver-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>> —
>>
>>
>>
>>
>>
>>
>>
>>
>> *Tim Sutton*
>>
>> *Co-founder:* Kartoza
>> *Ex Project chair:* QGIS.org
>>
>> Visit http://kartoza.com to find out about open source:
>>
>> Desktop GIS programming services
>> Geospatial web development
>> GIS Training
>> Consulting Services
>>
>> *Skype*: timlinux
>> *IRC:* timlinux on #qgis at freenode.net
>>
>> I'd love to connect. Here's my calendar link
>>  to make finding time easy.
>>
>>
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Joining the GeoServer meeting?

2019-09-17 Thread Tim Sutton

Hi

Yes I will be there today (17th) or did the date change?

Regards

Tim

> On 17 Sep 2019, at 03:54, Jody Garnett  wrote:
> 
> Torben has sent out the reminder, I hope you both can attend tomorrow.
> --
> Jody Garnett
> 
> 
> On Wed, 4 Sep 2019 at 00:17, Tim Sutton  > wrote:
> Hi
> 
> Cool - Jan has contacted me off list too. I will try to join the call too - 
> along with Admire who actually does all the hard work maintaining our 
> GeoServer docker image.
> 
> Regards
> 
> Tim
> 
>> On 4 Sep 2019, at 05:46, Jody Garnett > > wrote:
>> 
>> Thanks Jan, Tim Sutton (CCed) also expressed an interest in this activity.
>> 
>> Our next meeting is in two weeks (Sep 17) the meeting details are:
>> 
>> Jitsi: https://meet.jit.si/GeoServerMeeting 
>> 
>> Meeting time: 16:30 UTC 
>> 
>> 
>>  
>> Ideally
>>  we send a meeting reminder to this list before hand.
>> --
>> Jody Garnett
>> 
>> 
>> On Tue, 3 Sep 2019 at 09:37, Jan Boonen > > wrote:
>> Hi everyone,
>> 
>> This FOSS4G I tried to contribute to GeoTools and GeoServer for the first 
>> time during the code sprint and it was fun. One of the results was an 
>> interesting chat with Jody on creating an official Docker image of 
>> GeoServer. I'm very happy to contribute on this and have 
>> 
>> If possible I'd like to talk with you about this during the bi-weekly 
>> GeoServer meeting. Could somebody let me know when the meeting takes place 
>> and how I can join the meeting?
>> 
>> Kind regards,
>> 
>> Jan
>> 
>> --
>> Geodan
>> Buitenhaven 27-A
>> 5211 TP 's-Hertogenbosch (NL)
>> 
>> T +31 (0)73 - 692 5151
>> M +31 (0)6 - 2395 1191
>> E jan.boo...@geodan.nl 
>> www.geodan.nl  | disclaimer 
>> 
>> --
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net 
>> 
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel 
>> 
> 
> —
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Tim Sutton
> 
> Co-founder: Kartoza
> Ex Project chair: QGIS.org 
> 
> Visit http://kartoza.com  to find out about open source:
> 
> Desktop GIS programming services
> Geospatial web development
> GIS Training
> Consulting Services
> 
> Skype: timlinux 
> IRC: timlinux on #qgis at freenode.net 
> 
> I'd love to connect. Here's my calendar link  
> to make finding time easy.
> 

—









Tim Sutton

Co-founder: Kartoza
Ex Project chair: QGIS.org

Visit http://kartoza.com  to find out about open source:

Desktop GIS programming services
Geospatial web development
GIS Training
Consulting Services

Skype: timlinux 
IRC: timlinux on #qgis at freenode.net

I'd love to connect. Here's my calendar link  to 
make finding time easy.

___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11 #1251

2019-09-17 Thread Jenkins

See 



___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-9336) Integration test for WFSDataStore when doing a GetFeature operation having special chars in PropertyName

2019-09-17 Thread Marco Volpini (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
  Marco Volpini  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-9336  
 
 
  Integration test for WFSDataStore when doing a GetFeature operation having special chars in PropertyName   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 17/Sep/19 12:02 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
  Marco Volpini   
 

  
 
 
  
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS 
  
 
 
 This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100109-sha1:d720e51)

[Geoserver-devel] [JIRA] (GEOS-9335) WFS 2.0 Stored Queries return a not-managed NPE

2019-09-17 Thread Alessio Fabiani (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
  Alessio Fabiani  created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-9335  
 
 
  WFS 2.0 Stored Queries return a not-managed NPE   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 17/Sep/19 11:54 AM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
  Alessio Fabiani   
 

  
 
 
 
 

 
 I recently tried to create a WFS stored query, defined as follows: ```   xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fes="http://www.opengis.net/fes/2.0" xmlns:wfs="http://www.opengis.net/wfs/2.0" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xlink="http://www.w3.org/1999/xlink" id="riskDataStoredQuery"> Stored Query for geonode:risk_analysis_data   returnFeatureTypes="" language="urn:ogc:def:queryLanguage:OGC-WFS::WFS_QueryExpression" isPrivate="false">the_geom $ {AreaOfInterest}   ``` Trying to invoke this by providing the "STOREDQUERY_ID" param to GeoServer, leads to a NullPointerException which is wrapped by the response but not tracked at all on the GeoServer logs.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment

[Geoserver-devel] Build failed in Jenkins: geoserver-java11 #1250

2019-09-17 Thread Jenkins

See 

--
[...truncated 3.26 MB...]
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/qpid/qpid-broker-plugins-amqp-msg-conv-0-10-to-1-0/6.0.3/qpid-broker-plugins-amqp-msg-conv-0-10-to-1-0-6.0.3.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/qpid/qpid-broker-plugins-derby-store/6.0.3/qpid-broker-plugins-derby-store-6.0.3.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/qpid/qpid-broker-plugins-jdbc-provider-bone/6.0.3/qpid-broker-plugins-jdbc-provider-bone-6.0.3.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/derby/derby/10.11.1.1/derby-10.11.1.1.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/jolbox/bonecp/0.7.1.RELEASE/bonecp-0.7.1.RELEASE.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/qpid/qpid-broker-plugins-jdbc-store/6.0.3/qpid-broker-plugins-jdbc-store-6.0.3.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/qpid/qpid-broker-plugins-management-http/6.0.3/qpid-broker-plugins-management-http-6.0.3.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/eclipse/jetty/jetty-server/9.4.18.v20190429/jetty-server-9.4.18.v20190429.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/geronimo/specs/geronimo-servlet_3.0_spec/1.0/geronimo-servlet_3.0_spec-1.0.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/eclipse/jetty/jetty-http/9.4.18.v20190429/jetty-http-9.4.18.v20190429.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/eclipse/jetty/jetty-io/9.4.18.v20190429/jetty-io-9.4.18.v20190429.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/eclipse/jetty/jetty-servlet/8.1.17.v20150415/jetty-servlet-8.1.17.v20150415.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/eclipse/jetty/jetty-security/8.1.17.v20150415/jetty-security-8.1.17.v20150415.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/dojotoolkit/dojo/1.10.3/dojo-1.10.3-distribution.zip
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/qpid/qpid-broker-plugins-management-jmx/6.0.3/qpid-broker-plugins-management-jmx-6.0.3.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/qpid/qpid-broker-plugins-memory-store/6.0.3/qpid-broker-plugins-memory-store-6.0.3.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/apache/qpid/qpid-broker-plugins-websocket/6.0.3/qpid-broker-plugins-websocket-6.0.3.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/eclipse/jetty/jetty-websocket/8.1.17.v20150415/jetty-websocket-8.1.17.v20150415.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/org/eclipse/jetty/jetty-util/9.4.18.v20190429/jetty-util-9.4.18.v20190429.jar
[INFO] Downloading from geosolutions: 
http://maven.geo-solutions.it/com/rabbitmq/amqp-client/4.0.0/amqp-client-4.0.0.jar
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/qpid/qpid-broker/6.0.3/qpid-broker-6.0.3.jar
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/qpid/qpid-broker-core/6.0.3/qpid-broker-core-6.0.3.jar
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/qpid/qpid-management-common/6.0.3/qpid-management-common-6.0.3.jar
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/bcel/bcel/5.2/bcel-5.2.jar
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/org/apache/qpid/qpid-common/6.0.3/qpid-common-6.0.3.jar
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/qpid/qpid-broker/6.0.3/qpid-broker-6.0.3.jar
 (18 kB at 2.5 MB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/ch/qos/logback/logback-classic/1.1.3/logback-classic-1.1.3.jar
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/org/apache/qpid/qpid-management-common/6.0.3/qpid-management-common-6.0.3.jar
 (37 kB at 5.3 MB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/ch/qos/logback/logback-core/1.1.3/logback-core-1.1.3.jar
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/ch/qos/logback/logback-classic/1.1.3/logback-classic-1.1.3.jar
 (281 kB at 19 MB/s)
[INFO] Downloading from central: 
https://repo.maven.apache.org/maven2/commons-cli/commons-cli/1.2/commons-cli-1.2.jar
[INFO] Downloaded from central: 
https://repo.maven.apache.org/maven2/ch/qos/logback/logback-core/1.1.3/logback-core-1.1.3.jar
 (455 kB at 27 MB/s)
[INFO] Downloading from central:

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11 #1259

[Geoserver-devel] [JIRA] (GEOS-9337) Add Date Created and Date Modified in administration UI lists (layers, styles, ...)

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11-qa #1018

[Geoserver-devel] Build failed in Jenkins: geoserver-java11-qa #1017

[Geoserver-devel] Build failed in Jenkins: geoserver-java11 #1258

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11 #1257

[Geoserver-devel] Build failed in Jenkins: geoserver-java11 #1256

Re: [Geoserver-devel] GSIP-176

Re: [Geoserver-devel] GSIP-176

Re: [Geoserver-devel] GSIP-176

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11-qa #1011

[Geoserver-devel] Build failed in Jenkins: geoserver-java11-qa #1010

[Geoserver-devel] GeoTools / GeoServer PMC meeting - 2019-09-17

Re: [Geoserver-devel] Joining the GeoServer meeting?

Re: [Geoserver-devel] GSIP-176

[Geoserver-devel] Jenkins build is back to normal : geoserver-2.15.x-java11 #216

Re: [Geoserver-devel] GSIP-176

Re: [Geoserver-devel] Joining the GeoServer meeting?

Re: [Geoserver-devel] Joining the GeoServer meeting?

[Geoserver-devel] Jenkins build is back to normal : geoserver-java11 #1251

[Geoserver-devel] [JIRA] (GEOS-9336) Integration test for WFSDataStore when doing a GetFeature operation having special chars in PropertyName

[Geoserver-devel] [JIRA] (GEOS-9335) WFS 2.0 Stored Queries return a not-managed NPE

[Geoserver-devel] Build failed in Jenkins: geoserver-java11 #1250

23 matches

Site Navigation

Mail list logo

Footer information