Re: [Geoserver-devel] [Geowebcache-devel] GSIP 168, skip beta releases and remove feature freeze

+1 -Jukka Rahkonen- Lähettäjä: Kevin Smith [mailto:smit...@draconic.ca] +1 On 2018-04-15 07:24 AM, Ian Turton wrote: +1 Ian On 15 April 2018 at 09:52, Andrea Aime mailto:andrea.a...@geo-solutions.it>> wrote: Hi, as promised here is the GSIP for the release procedure change we've already ap

Re: [Geoserver-devel] [Geowebcache-devel] GSIP 168, skip beta releases and remove feature freeze

+1 On 2018-04-15 07:24 AM, Ian Turton wrote: > +1 > > Ian > > On 15 April 2018 at 09:52, Andrea Aime > wrote: > > Hi, > as promised here is the GSIP for the release procedure change > we've already applied to 2.13.x: > > https://github.com/geo

[Geoserver-devel] [JIRA] (GEOS-8703) WFS 2.0 capabilities report transaction support even if the service level is not configured as such

Title: Message Title Andrea Aime created a

[Geoserver-devel] [JIRA] (GEOS-8702) Once set, the NSG versioning time properties might not be modyable anymore via the UI

Title: Message Title Andrea Aime created a

[Geoserver-devel] [JIRA] (GEOS-8701) Importer rest interface does not configure time dimension when a DateFormatTransform is defined on tasks

Title: Message Title Alessio Fabiani creat

[Geoserver-devel] [JIRA] (GEOS-8700) NSG VersioningFilterAdapter breaks usage of FID filters

Title: Message Title Andrea Aime created a

[Geoserver-devel] [JIRA] (GEOS-8699) WCS 2.0.1 subsetting with other CRS does not follow the standard

Title: Message Title Jukka Rahkonen create

[Geoserver-devel] [JIRA] (GEOS-8698) Windows Installer: Remove 'work' folder when uninstalling

Title: Message Title Ronald Hoek created a

[Geoserver-devel] [JIRA] (GEOS-8697) Remove language warnings during Windows setup compilation

Title: Message Title Ronald Hoek created a

[Geoserver-devel] [JIRA] (GEOS-8696) WFS 3.0 won't work off a workspace specific endpoint

Title: Message Title Andrea Aime created a

Re: [Geoserver-devel] Introduction

On Wed, Apr 18, 2018 at 2:43 PM, Ronald Hoek - ComponentAgro B.V. < ronald.h...@componentagro.nl> wrote: > Hello Andrea, > > > > For testing I now used the ‘bin.zip’ content (as I don’t; have the > environment set up for building GeoServer). > > > > I’ve created a pull request (on the master) to c

Re: [Geoserver-devel] Introduction

Hello Andrea, For testing I now used the ‘bin.zip’ content (as I don’t; have the environment set up for building GeoServer). I’ve created a pull request (on the master) to change the installer behavior (pull contains two commits). However I have two more (smaller) issues, which I fixed too:

Re: [Geoserver-devel] OAuth2

A tickbox would be a great idea I guess. Currently on our use cases (GeoNode) we need things to be stateless, and therefore on that plugin I just ignore anything but query string access_token. For the gui I rely on JSESSION ID. This approach does not work for google and github unfortunately. Rega

[Geoserver-devel] [JIRA] (GEOS-8695) High security vulnerability has been found in the Pivotal Spring Framework

Title: Message Title Lukas Kosowski create

Re: [Geoserver-devel] Introduction

On Wed, Apr 18, 2018 at 11:27 AM, Ronald Hoek - ComponentAgro B.V. < ronald.h...@componentagro.nl> wrote: > Hello Andrea, > > > > I’ve taken a bit of time to look into the NSIS ‘world’ and when I look at > the script, it seems is requires file base on the location the script file > if located. > >

Re: [Geoserver-devel] Introduction

Hello Andrea, I’ve taken a bit of time to look into the NSIS ‘world’ and when I look at the script, it seems is requires file base on the location the script file if located. However, it looks like these files are scattered across the repo, which requires me to create a copy of these file for

Re: [Geoserver-devel] Why Install as Windows service requires 32 bit JRE?

On Wed, Apr 18, 2018 at 11:00 AM, Rahkonen Jukka (MML) < jukka.rahko...@maanmittauslaitos.fi> wrote: > Hi, > > > > What is the reason that installing Geoserver as a Windows service with the > Windows installer requires 32 bit JRE? Is it because the service wrapper is > architecture dependent and 6

[Geoserver-devel] Why Install as Windows service requires 32 bit JRE?

Hi, What is the reason that installing Geoserver as a Windows service with the Windows installer requires 32 bit JRE? Is it because the service wrapper is architecture dependent and 64 bit version is not even available as Community edition https://wrapper.tanukisoftware.com/doc/english/download

Re: [Geoserver-devel] Reminder: GeoTools / GeoServer meeting at 15:30 UTC on Tuesday

I was on site with a client and couldn't make it either :-( Ian On 17 April 2018 at 21:42, Jody Garnett wrote: > Sorry I am out sick today and could not attend. > > On Tue, Apr 17, 2018 at 8:57 AM Andrea Aime > wrote: > >> The time passed and saw no activity on skype... I'm assuming it got >>

Re: [Geoserver-devel] Introduction

Hi Ronald, thanks for joining and introducing yourself. Find my comments below inline. On Mon, Apr 16, 2018 at 3:31 PM, Ronald Hoek - ComponentAgro B.V. < ronald.h...@componentagro.nl> wrote: > But as always all software has issues ( https://osgeo-org.atlassian. > net/browse/GEOS-8683 ). > > > >

Re: [Geoserver-devel] Monitoring hibernate module: does it have a maintainer?

Hi, We do use it and to my knowledge it is working fine at present. I'm not saying we will definitely continue to use it but is it possible the lack of updates is just because it isn't broken? Anyway, I can't volunteer as I still haven't managed to get any training to up my confidence level an

Re: [Geoserver-devel] OAuth2

We would like to disable passing the bearer token in the URL (including query string), since this is not recommended, and in some security standards is not allowed - Don't pass bearer tokens in page URLs: Bearer tokens SHOULD NOT be passed in page URLs (for example as query string

Re: [Geoserver-devel] Monitoring hibernate module: does it have a maintainer?

On Wed, Apr 18, 2018 at 10:03 AM, Paul Wittle wrote: > Hi, > > We do use it and to my knowledge it is working fine at present. I'm not > saying we will definitely continue to use it but is it possible the lack of > updates is just because it isn't broken? > Hum.. how do you use it? We tried it,