[Geotools-devel] Using native filters in queries

2018-03-19 Thread Nuno Oliveira
Hi all, Recently I have been dealing with some use cases that require the ability to inject some native filters, specific for each feature type and non static over time, to the final native query build by GeoTools and send to the data store. For example, the content of a feature type is parti

Re: [Geotools-devel] Replace JScience JSR275 with JSR363

2018-03-19 Thread César Martínez Izquierdo
Hi, It is my intention to provide GWS/GS pull requests if needed, obviously I'll be happy if someone wants to help on it. For the moment I'm going to work on a PR for Geotools, then I'll evaluate how painful it was and what is needed for GWC/GS. Best regards, César On 19 March 2018 at 16:05, An

Re: [Geotools-devel] Before reformatting everything, slight change in coding conventions?

2018-03-19 Thread Ben Caradoc-Davies
On 19/03/18 20:12, Andrea Aime wrote: On Sun, Mar 18, 2018 at 11:02 PM, Ben Caradoc-Davies wrote: We could fork the Google tool. Yes... and then fork the maven plugin build around it too. And then keep the fork up to date as new fixes and language features come out. Time is better spent fixing

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

2018-03-19 Thread Ben Caradoc-Davies
GeoTools / GeoServer committee meeting on Skype at 15:30 UTC on Tuesday: https://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+/+GeoServer+Meeting&year=2018&month=3&day=20&hour=15&min=30&sec=0&ah=1 -- Ben Caradoc-Davies Director Transient Software Limited New

Re: [Geotools-devel] Google formatting, a second look

2018-03-19 Thread Eric Engle via GeoTools-Devel
Just my $.02, as a long-time lurker who would love to simplify contributions as much as possible: I use 2 space indentation in my day job, and contributing some of that work upstream to you is certainly simpler if that also uses two spaces ;-] Best regards, Eric On Sun, Mar 18, 2018 at 3:22 AM

Re: [Geotools-devel] Replace JScience JSR275 with JSR363

2018-03-19 Thread Andrea Aime
Hi Jody, looks good, will you also have corresponding GWC/GS pull requests (if at all needed, of course)? Cheers Andrea On Mon, Mar 19, 2018 at 3:56 PM, Jody Garnett wrote: > We have been working today and have made the following proposal: > - https://github.com/geotools/geotools/wiki/Migrate-U

Re: [Geotools-devel] Replace JScience JSR275 with JSR363

2018-03-19 Thread Jody Garnett
We have been working today and have made the following proposal: - https://github.com/geotools/geotools/wiki/Migrate-Units-to-JSR-363 So far no surprises, we will be in tomorrows GeoTools meeting if there are any questions, and would like to proceed with a pull request this week. -- Jody Garnett

Re: [Geotools-devel] GeoTools 19.0 artifacts available for testing

2018-03-19 Thread Alessandro Parma
Thanks Andrea, Proceeding with the release Regards, Alessandro Il giorno lun 19 mar 2018 alle ore 14:06 Andrea Aime < andrea.a...@geo-solutions.it> ha scritto: > Hi Alessandro, > did a fully build off an empty repo, looking good! > > Cheers > Andrea > > On Mon, Mar 19, 2018 at 10:41 AM, Alessand

Re: [Geotools-devel] GeoTools 19.0 artifacts available for testing

2018-03-19 Thread Andrea Aime
Hi Alessandro, did a fully build off an empty repo, looking good! Cheers Andrea On Mon, Mar 19, 2018 at 10:41 AM, Alessandro Parma < alessandro.pa...@geo-solutions.it> wrote: > Artifacts are available here: https://build.geoserver.org/ > geotools/release/19.0 > > Any help testing is appreciated

[Geotools-devel] GeoTools 19.0 artifacts available for testing

2018-03-19 Thread Alessandro Parma
Artifacts are available here: https://build.geoserver.org/geotools/release/19.0 Any help testing is appreciated Thank you and Regards, Alessandro -- == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Alessandro Parma Junior DevOps GeoSolutio

Re: [Geotools-devel] Before reformatting everything, slight change in coding conventions?

2018-03-19 Thread Andrea Aime
On Sun, Mar 18, 2018 at 11:02 PM, Ben Caradoc-Davies wrote: > We could fork the Google tool. Yes... and then fork the maven plugin build around it too. And then keep the fork up to date as new fixes and language features come out. Time is better spent fixing actual GT/GWC/GS issues imho, but...