Huh, interesting.
Looks like at least one of the submodule links in Justin's repo are broken
(goes to a 404), so migration may be interesting.
I found the official cite test repo, and it look like this failure may have
been fixed 1.5 years ago: https://github.com/opengeospatial/ets-wfs11/
commit/bf25d9c689997f851692f973006bcbd3eae54a18
On Fri, May 12, 2017 at 4:19 PM, Ben Caradoc-Davies <b...@transient.nz>
wrote:
> On 13/05/17 11:13, Torben Barsballe wrote:
>
>> On Fri, May 12, 2017 at 4:08 PM, Ben Caradoc-Davies <b...@transient.nz>
>> wrote:
>>
>>> How about:
>>> 3. Update the failing CITE tests to reflect the existence of WFS 2.0.0.
>>>
>> That would certainly be the better option. However, the CITE tests their
>> own project / repo, and I am not especially familiar with it.
>> Plus, I'm not sure how easy it is to update the version of the CITE engine
>> we have running on ares. Has anyone done this recently?
>>
>
> The CITE tools are in their own repo:
> https://github.com/geoserver/geoserver-cite-tools
>
> The tests are in a submodule that points to Justin's repo:
> https://github.com/jdeolive/cite-scripts/tree/9937bd36c2377f
> 7692ab7856307f78a067de8112
>
> History indicates that Justin has previously had to fix a few problems in
> the tests.
>
> Should we fork this back into a new repo in the GeoServer organisation to
> make it easier for us to maintain?
>
> Kind regards,
>
>
> --
> Ben Caradoc-Davies <b...@transient.nz>
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
