On Sun, Feb 9, 2014 at 10:20 PM, Allen Lin wrote:
> Hi Jody,
>
> Thanks for pointing that out, though I am having two more questions:
> 1) What to be included in the test case? Says, for Parsing WFS GetFeature
> response from ArcGIS Server, should I make a WFS FeatFeaturePOST request to
> one Arc
Looks like we have enough votes to proceed. Linked to the google doc.
Filled in the release schedule:
http://geoserver.org/display/GEOS/GeoTools+and+GeoServer+release+schedule
Currently I have both individual branch schedule, and a combined schedule
(thanks to text editor sort). I think I like
You should be able to copy one of the existing tests cases, many of them
contain the sample output which is fed into the WFS Client code. Your test
case can show that the current code fails, and then when the developer
applies you patch they can verify that your fix works.
You can sign up to Jira
+1. Thanks Jody.
And thanks to Andrea and Alessio, who IIRC originated the idea. Perhaps
add a link to Andrea's Google Doc?
Kind regards,
Ben.
On 06/02/14 11:13, Jody Garnett wrote:
> Proposal is up:
>
> http://docs.codehaus.org/display/GEOTOOLS/Extended+Release+Schedule
>
> In writing it up I
Hi Jody,
Thanks for pointing that out, though I am having two more questions:
1) What to be included in the test case? Says, for Parsing WFS GetFeature
response from ArcGIS Server, should I make a WFS FeatFeaturePOST request to
one ArcGIS Server and parsing that using the Patched class I wrote?
2
Title: Message Title
Christian Mueller created an issue
Title: Message Title
Christian Mueller created an issue
So I understand what is being proposed. I suppose my questions twofold a)
what is your time frame for this work and b) why 10.x ( since we are
nearing the 11.0)?
As for moving code between projects, everything looks okay. For the
GeoServer code subject to a license change we will need a email requ
