And I kicked Hudson geotool-master for good measure. Once the artifacts
are deployed, geoserver should build cleanly.
On 21/08/12 09:37, Ben Caradoc-Davies wrote:
> geotools-master was broken by an intermittent wfs-ng failure that I have
> seen elsewhere from time to time. This caused Niels' 3D c
geotools-master was broken by an intermittent wfs-ng failure that I have
seen elsewhere from time to time. This caused Niels' 3D changes to not
be published to the repo.
Failed tests:
testGetFeatureLockingExpire(org.geotools.data.wfs.integration.MemoryDataStoreIntegrationTest):
fid-3c6d8b2_13
I just ran into this as well (and "forcing a refresh" via mvn -U install
doesn't resolve the issue.)
I would schedule a Hudson build to put the new jars into the maven repo,
but apparently the build for geotools master is failing in Hudson right
now. It looks like this error is not a problem with
That class was recently added to geotools master; try and force a refresh
or build geotools locally.
--
Jody Garnett
On 20/08/2012, at 10:40 PM, "Severin (aka Cliff)"
wrote:
Hi Geoserver dev's,
I sat down for a hack on GeoServer this evening and am running up against a
brick wall while attempt
Hi Geoserver dev's,
I sat down for a hack on GeoServer this evening and am running up against a
brick wall while attempting to build with maven.
I am following
http://docs.geoserver.org/stable/en/developer/quickstart/index.html
yet when a 'mvn clean install' from geoserver/src is attempted, I am
