Hi all,
I poked at this a little bit today. I managed to find some common
patterns, so I worked across the code base and knocked out a few smaller
modules.
When I tried gt-coverage, I hit issues with JAI using raw Maps. Should
the plan there be to Suppress those readily?
In
Okay, caught up problem after the release went out, unpublished the blog
posts while fixing.
New tested revisions from a nightly build:
version = 2.17-SNAPSHOT
git revision = e65d01375e96a9c1c0daf075c65741e41071acd5
git branch = origin/2.17.x
build date = 22-Jul-2020 04:41
geotools version =
That is really funny, and your PR looks good.
--
Jody Garnett
On Wed, 22 Jul 2020 at 06:17, Andrea Aime
wrote:
> Well,
> given the issue arises because importer pom.xml depends on ArcSDE, and it
> should really not,
> this is the simplest solution:
>
>
Well,
given the issue arises because importer pom.xml depends on ArcSDE, and it
should really not,
this is the simplest solution:
https://github.com/geoserver/geoserver/pull/4430
Cheers
Andrea
On Wed, Jul 22, 2020 at 12:41 PM Andrea Aime
wrote:
> Hi,
> funny issue showing up in our build
Hi Paul,
I haven’t had the time to look into it yet, but thinking about a solution is
part of our current development sprint that started on Monday. There are some
items I have to work on before, but I assume that I can start next Monday at
the latest.
Can you maybe send me instructions to
Hi,
funny issue showing up in our build checks, see here:
https://osgeo-org.atlassian.net/browse/GEOS-9702
Seems like someone dedicated that Java 8 would never have more than 256
releases... but it did :-D
We'll have to upgrade the library...
Cheers
Andrea
== GeoServer Professional Services
