> > I don't care if we run the cite tests a bit slower. > What I'm worried about is that we would remove some test coverage on > the case that people do really run in production, since the CITE tests > would not test it anymore. > Are you sure our unit tests provide the same coverage over GML encoding > as the cite tests do? Fair enough, that is a very valid concern. We can continue to maintain the test coverage we achieve now by running the old encoder with the old postgis setup. But keep in mind that I am the only one who runs and fixes cite tests for releases (or at least I am one that usually does it). Maintaining a hacked cite setup is not something I am crazy about, and probably something i don't have the capacity for. Would someone else be willing to take on the responsibility of running these tests?
So an option to enable the new GML2 output format only when running certain cite suites is deemed ok? > > Cheers > Andrea -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
