Yup, I have yet to port the mock tests to the new configuration. Although 99% of the tests work transparently with the new data directory. The only tests that have issues are ones that change the data directory in place and reload the catalog in the test case. This requires a bit of hacking on the base classes. There is a jira already open for this one:
http://jira.codehaus.org/browse/GEOS-2729 -Justin Ben Caradoc-Davies wrote: > Justin Deoliveira wrote: >> Those of you watch the commit logs will notice I committed my changes >> for GSIP 34 :). What this means is: >> 1) the new data directory is in effect. So the first time you start up >> geoserver with your current data directory it will be "morphed" as >> outlined by the proposal. > > Does this happen when GeoServerAbstractTestSupport is invoked by JUnit? > That is, has MockData been ported? I guess I can answer my own question > by looking at HEAD: > > In GeoServerAbstractTestSupport: > > //HACK: once we port tests to the new data directory, remove this > GeoServerLoader.setLegacy( true ); > > I assume this suppresses the morphing, and that MockData has not yet > been ported. > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
