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

Hi Gabriel, Andrea, no experience with that automation, but I would say +1. Just cleaned my dangling branch: >$ git for-each-ref --sort=authorname --format="%(committerdate) %09 %(authorname) %09 %(refname)" refs/remotes/upstream | grep "Nuno Oliveira" Thu Oct 3 22:57:07 2019 +0200Nuno

Re: [Geoserver-devel] GSIP 182 - Show a tab and table of roles for each layer, layer group, workspace

Hi Jody, thank you for the feedback, please check my replies bellow: On Wed, Oct 16, 2019 at 11:44 PM Jody Garnett wrote: > I like the idea, care should be taken in the description as this is not > the only security consideration in play when trying to access a layer. > > Thoughts for

Re: [Geoserver-devel] Vote on GSIP 178

an we change that around so what is being > voted on is more clear? > > * Proposal: We propose adding enabled and advertised flags to > PublishedInfo ... > > * Feedback: We considered option 1 and option 2 below ... > > -- > Jody Garnett > > > On Thu, 3 Oct 2019 at

Re: [Geoserver-devel] Vote on GSIP 178

ct 4, 2019 at 10:01 AM Andrea Aime >> wrote: >> >>> Hi Nuno, >>> works for me, +1 >>> >>> Just a note, the proposal talks about displaying "time", but it's really >>> a timestamp >>> >>> Cheers >>>

Re: [Geoserver-devel] Vote on GSIP 179

-Created-and-Date-Modified-in-administration-UI-lists-layers-styles-td5413744.html The proposal links to the relevant JIRA ticket and pull request. Thank you, Nuno Oliveira On Thu, Oct 3, 2019 at 10:40 PM Nuno Oliveira GeoSolutions < nuno.olive...@geo-solutions.it> wrote: > Dear PSC memebe

Re: [Geoserver-devel] Vote on GSIP 178

equest. Thank you, Nuno Oliveira On Thu, Oct 3, 2019 at 11:02 PM Nuno Oliveira GeoSolutions < nuno.olive...@geo-solutions.it> wrote: > Dear PSC memebers, > > I would kindly ask you to cast a vote on: > https://github.com/geoserver/geoserver/wiki/GSIP-178 > <https://github.com

[Geoserver-devel] Vote on GSIP 178

Dear PSC memebers, I would kindly ask you to cast a vote on: https://github.com/geoserver/geoserver/wiki/GSIP-178 This thread is for the voting process, the discussion thread is available here:

[Geoserver-devel] Vote on GSIP 179

Dear PSC memebers, I would kindly ask you to cast a vote on: https://github.com/geoserver/geoserver/wiki/GSIP-179 This thread is for the voting process, the discussion thread is available here:

Re: [Geoserver-devel] GSIP 180 discussion: committer list cleanup and committer requirements

Look s like a good proposal to me, fair and straightforward rules. On Mon, Sep 23, 2019 at 8:59 AM Ian Turton wrote: > Looks fine to me +1 > > Ian > > On Sun, 22 Sep 2019 at 10:13, Andrea Aime > wrote: > >> Hi, >> the committer list in GeoServer is in a outdated/messy state, the >> following

Re: [Geoserver-devel] GSIP 175 - Promote status monitoring module from Community to Extension

Hi Jody, my apologies for the feedback delay, please find my answers bellow: On Tue, Jun 18, 2019 at 8:38 PM Jody Garnett wrote: > That looks useful, tab for "module" status was intended to capture some of > this information as well but was never followed up on. > > 0. status monitoring

Re: [Geoserver-devel] Build not running on Intellij

Glad to hear it! On Tue, Nov 27, 2018 at 7:23 PM Thomas wrote: > I have gotten everything working by cleaning everything and then the > errors changed. I have also solved those issues. > > Thanks, > Thomas > > On Tue, Nov 27, 2018 at 10:16 AM Nuno Oliveira GeoSolutions

Re: [Geoserver-devel] Build not running on Intellij

> > When you say I don't need the -DskipTests, is that because it is only used > while building? Yes, this is an option that is only relevant to Maven. Well in that case I can only suggest you try to understand why your IDE is not able to access:

Re: [Geoserver-devel] Can we turn off the issue tracker on https://github.com/geoserver/geoserver.github.io?

+1 On Sat, Nov 24, 2018 at 12:16 AM Torben Barsballe < tbarsba...@boundlessgeo.com> wrote: > I agree, easier to have everything in one place. > > Although if we do turn issues off, we should probably also add a link to > JIRA in the README. > > Torben > > On Thu, Nov 22, 2018 at 10:42 AM Andrea

Re: [Geoserver-devel] Merging the JDK11 branches back to master, GS and GWC

+1 On Fri, Oct 26, 2018 at 8:47 AM Andrea Aime wrote: > Hi all, > the gwc/gs JDK11 branches are in a good shape for merging, they build and > run in our quick tests. > I'd like to merge to master as they are, before the EMF changes, and > evaluate the situation > CITE tests wise, and then get

Re: [Geoserver-devel] Log4j upgrade... like right now... yep, I mean it

Ok fair enough, so +1 for the new directory. On Tue, Oct 23, 2018 at 1:50 PM Andrea Aime wrote: > On Tue, Oct 23, 2018 at 1:36 PM Nuno Oliveira GeoSolutions < > nuno.olive...@geo-solutions.it> wrote: > >> Wondering, would it not be easier to: >> >>1. us

Re: [Geoserver-devel] Log4j upgrade... like right now... yep, I mean it

Hi Andrea, please see my answers bellow: On Tue, Oct 23, 2018 at 10:30 AM Andrea Aime wrote: > Hi, > months ago Jody wrote a proposal to upgrade Log4j to the latest version > (2.x), the proposal is still here > but has had little discussion and no voting: >

Re: [Geoserver-devel] Stepping down from GeoServer PSC

Likewise, and thank you for tall the help and discussion around App-Schema !!! On Tue, Oct 23, 2018 at 8:54 AM Ian Turton wrote: > Sorry to hear this, but thanks for all your hard work over the years. > > Ian > > On Mon, 22 Oct 2018 at 22:27, Ben Caradoc-Davies wrote: > >> I hereby step down

Re: [Geoserver-devel] Complex features - Encoding XML attributes in GeoJSON

Thu, Oct 11, 2018 at 2:06 PM Andrea Aime wrote: > On Thu, Oct 11, 2018 at 2:55 PM Nuno Oliveira GeoSolutions < > nuno.olive...@geo-solutions.it> wrote: > >> My suggestion is to encode XML\GML attributes as an array of values, >> using the example

[Geoserver-devel] Complex features - Encoding XML attributes in GeoJSON

Dear all, Currently, the complex features GeoJSON encoder [1] doesn't encode XML (GML) attributes. For example, something like: (...) *200.0* (...) Will be encoded like this in GeoJSON: (...) "properties": { "gsml:positionAccuracy": { "gsml:CGI_NumericValue": {