Bryce L Nordgren a écrit : > Building GeoAPI not required. GeoAPI would release more than one target > jar, just like GT modules and plugins are packaged in different jars. > > GT Modules would include this in their POM: > > <dependency> > <name>GeoAPI-test-geometry</name> > <scope>test</scope> > <version>2.1</version> > </dependency>
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. Jody's argument (avoid to make Geotools harder to maintains for developpers who are not both Geotools and GeoAPI members) is right too. Furthermore, we may not have the energy to refactor existing Geotools tests as GeoAPI tests soon. But in the particular case of geometries, new test suites are needed and the contributors are willing to write them as GeoAPI tests. I believe that it is worth a try. If we can attract non-Geotools developpers in addition of current ones, it would be a win for both GeoAPI and Geotools (more complete test coverage for us). For example Geoxygene (http://oxygene-project.sourceforge.net/) is (or was) about geometries and is totally unrelated to Geotools. Martin. _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
