It can be found near the top of the screen; only works for open issues
though.
--
Jody Garnett
On 18 December 2016 at 12:29, Ben Caradoc-Davies wrote:
> I do not see an "evaluate" button.
>
> Jody, who can see it, and where can it be found?
>
> Kind regards,
> Ben.
>
> On 19/12/16 07:13, Andrea
Thanks for the heads up Ben. Looks like those didn't make it into the
latest set of CITE tests, so I'll kick off a new run before starting the
release.
Torben
On Sun, Dec 18, 2016 at 12:13 PM, Ben Caradoc-Davies
wrote:
> Torben,
>
> I also cherry picked onto 16.x a WKT encoding fix for Azimutha
Ah! Thanks very much Jody, I see it. I was looking at issues that had
left the Open state.
Kind regards,
Ben.
On 19/12/16 21:07, Jody Garnett wrote:
> It can be found near the top of the screen; only works for open issues
> though.
>
> --
> Jody Garnett
>
> On 18 December 2016 at 12:29, Ben Cara
The 16.1 artifacts are available for testing at:
http://ares.boundlessgeo.com/geotools/release/16.1
I am currently running a clean local build of these artifacts. If someone
else wants to test them as well, that would be appreciated.
Torben
Torben,
all looks good to me.
Artifact sizes similar to 16.0, api and users docs look OK, binaries
have sane versions and no SNAPSHOTs, and project zip builds cleanly with
an empty repo and online tests against postgres/postgis 9.6/2.3 on
Debian unstable:
mvn -s /path/to/maven/settings.xml -D
I am getting some unusually long build times for certain modules:
imagemosaic datasource module -> 18:50 min
NetCDF gridcoverage module -> 59:12 min
WFS client module (NG) -> 01:22 h
Most other other modules build in less than a minute.
Total build time is 3:05 h
Anyone else seeing this?
(I
Thanks for testing Ben.
Looks good from my testing as well. Proceeding with the release...
Torben
On Mon, Dec 19, 2016 at 2:30 PM, Ben Caradoc-Davies
wrote:
> Torben,
>
> all looks good to me.
>
> Artifact sizes similar to 16.0, api and users docs look OK, binaries have
> sane versions and no
I did not see this. My full test build completed in under 45 minutes
including download of all dependencies into an empty repo.
I have in the past seen some unusually long build times where tests
access network resources such as schemas. Network latencies and timeouts
can cause tests to hang fo
