Martin Desruisseaux wrote: > I did that for referencing, but unfortunatly can't do that for every > modules. Still I am more worried about doing this for every set of interfaces; interfaces are a commitment - and as project leaders in GeoAPI we take a lot of time to manually check the interfaces against the standards. I would like to see us try to check it against Java code as well.
Perhaps we can have an annotation called @pending that marks any interface what has not been implemented yet? >> Alternative ideas: >> - test cases showing sample use - even if they cannot be run? > We can do runnable test cases. A lot of GeoTools referencing test > cases could be moved as GeoAPI tests. The tests can search for a > factory in META-INF/services and run. Like usual the only reason why > it is not yet done is lack of time. Still I like the idea; test cases are like javadocs you can run. Perhaps if we thought instead of them as code examples (rather then conformance tests) it would make them easier to write. When we did the FeatureModel stuff I took this approach; made test cases to make sure the API made sense in code example form. We also had a lot of luck when Justin took the time to write up all the common uses for the feature model and put them all on the same page. Jody ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
