[Geoserver-devel] [JIRA] (GEOS-9402) Error message appears after clicking the logout button when creating a new vector data source

2019-11-19 Thread FB (JIRA)
Title: Message Title FB cre

[Geoserver-devel] [JIRA] (GEOS-9403) MongoDB Plugin breaks GeoServer Admin UI

2019-11-19 Thread FB (JIRA)
Title: Message Title FB cre

Re: [Geoserver-devel] Backporting [GEOS-9316] Support for vector custom dimensions

2019-11-19 Thread Nuno Oliveira
+1 On Tue, 2019-11-19 at 03:49 +0100, fernando.m...@geo-solutions.it wrote: > Hi Geoserver community, > > Since [GEOS-9316] Support for vector custom dimensions PR was merged > to master far more than one month ago(Sep 13), If you agree with > this, I would like to backport it to 2.16.x branch. >

Re: [Geoserver-devel] Backporting [GEOS-9316] Support for vector custom dimensions

2019-11-19 Thread Andrea Aime
+1, but please wait for 2.16.1 to be out before merging the backport PRs Cheers Andrea On Tue, Nov 19, 2019 at 3:50 AM fernando.m...@geo-solutions.it < fernando.m...@geo-solutions.it> wrote: > Hi Geoserver community, > > Since [GEOS-9316] Support for vector custom dimensions PR was merged to > m

Re: [Geoserver-devel] clean up canonial repo branches

2019-11-19 Thread Gabriel Roldan
Thanks Nuno for the command. I'm gonna start by deleting the following ones that are safe to remove: Already merged to (reachable from) master: git for-each-ref --sort=committerdate --format="%(committerdate:short),%(objectname:short),%(refname:short),\"%(authorname)\"" refs/remotes/upstream --me

Re: [Geoserver-devel] clean up canonial repo branches

2019-11-19 Thread Gabriel Roldan
Here's a compiled list of all branches whose future is yet to be decided: https://docs.google.com/spreadsheets/d/1Wg0gqbiXdwyb4lt_52UK4C9qnN6yj20vWRlbzlgpJgY/edit?usp=sharing I didn't have time yet to dig deeper into each one to recommend and action though. I've a backup of all the branches befor

[Geoserver-devel] Identical table names in different schemas

2019-11-19 Thread Uhrig, Stefan
Hi all, I just observed some odd behavior if there are two tables with the same name in two different schemas and the schema is left blank when adding a data store (I tested with PostGIS). In such a scenario, only one table is listed when you attempt to publish a new layer. However, in the "Ed