[EMAIL PROTECTED] wrote on 06/04/2006 06:45:28 PM:
> I believe that Bryce has a point. We can create a new GeoAPI module, > call it "geoapi-tests" or > something like that, and deploy them through the usual Maven 2 > mechanism. External projects like > Geotools and Geoserver can add this dependency in their Maven 2.0 > pom.xml file and get the GeoAPI > tests executed automatically every time Geotools is built, with no > effort on their side. Well, maybe not "no effort". The implementor has to supply implementations of GeometryFactory and PrimitiveFactory. But certainly it allows for a "minimal effort" jump start to testing. It also doesn't prohibit developers from writing tests in the GeoTools geometry module. This strategy just designates a retirement home for good, general purpose tests which are applicable to more than one implementation. They can start life somewhere else. As a curious coincidence, take a look at what you get if you download Jakarta's commons-collections. When you unpack the file, you get not only commons-collections-3.2.jar, but commons-collections-testframework-3.2.jar. The testframework is filled with "AbstractTests" against which one can test your own implementations. We wouldn't exactly be on the bleeding edge of technology if we were to adopt a similar strategy. :) Bryce _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
