I am with Andrea concerning the test coverage. I am always trying hard to get a good code coverage, investing sometimes more time in creating the the test cases than in the module itself.
Additionally, since I developed a Swing applet for showing maps and modifying geometries, I know Swing is a nasty thing. We had problems supporting both sun java 5 and sun java 6. I did not go further and check with ibm sdks or openjdk and made sun java 6 a prerequisite, over and out. This was only possible because the applet is a special application dedicated for about 100 users. From my point of view, there are 2 things I worry about. 1) As Andrea stated, 4% coverage is quite poor 2) I am afraid, thinking on the build servers I want to deploy, that there will be problems with IBM Hudson and OpenJDK Hudson. My proposal would be a) Integrate a Swing test framework into geotools b) Increase the code coverage c) check with different sdks, otherwise we have a time bomb here. The idea about the module is ok, a good starting point for developing. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
