I am very much in favour of this, will report back after testing.
On Sat, Dec 18, 2021 at 12:26 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:
> Hi,
> following the last PSC meeting, and after attempting to use spotless,
> I've realized we have a mix of line endings in our git
Please have a look at
https://github.com/geoserver/geoserver/wiki/GSIP-206 which outlines moving
different sections of the geopackage community module into the appropriate
core module: gs-wfs, gs-wms, and gs-wps.
The proposal is solid, please make note of the backwards compatibility
section which
I got a message from the windows build complaining about permissions; next
release cycle like to figure out what is going on.
Jody
On Wed, Dec 22, 2021 at 1:03 AM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:
> Hi all,
> the artifacts are available here:
>
>
Thanks Andrea!
GeoServer 1.x had some very simple ability to “override” attribute
information, it is nice to see that improved on. I wonder if this would
allow geopackage to force the geometry of an SQLView from BigDecimal to
Geometry.
I will read this more carefully tomorrow.
Jody
On Wed, Dec
Thanks Andrea, I have also found some of the closures getting deeply nested.
Jody
On Wed, Dec 29, 2021 at 6:06 AM Andrea Aime wrote:
> Hi all,
> I'd like to introduce a Checkstyle check that verifies lines are not too
> deeply nested.
> The Google format we are using is indenting excessively
Hi all,
I'd like to introduce a Checkstyle check that verifies lines are not too
deeply nested.
The Google format we are using is indenting excessively long lines that are
overflowing on the next line 8 chars instead of 4,
I believe as a way to discourage too deep nesting.
However, we have a lot
