Justin Deoliveira <[EMAIL PROTECTED]> wrote on 05/29/2006 04:12:47 AM:
> With the exception of a select few I do not expect many geotools > developers to actually build geoapi. Which would mean that the tests > that get moved out would be run less often which imho would decrease > their effectiveness. > -Justin 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> In response to Jody: nothing could be nicer to your developers than handing them a test suite on a silver platter. ;) The idea is to supply a reference test set from which implementors could pick and choose individual tests. Passing all tests should be a goal, but if it's cool to release code with "known bugs", then implementors could turn off tests which make them look bad. :) If it doesn't pass the test, it's not interoperable: users can't integrate GT and non-GT implementations. It may be something like returning null instead of an empty list. Doesn't matter what implementation it is, it should behave the same. Do you seriously consider it developer friendly to require that they write a test for every GeoAPI javadoc comment? :) Bryce ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
