Bleah ... this is the problem: a) do we get asserts to work (scope creep like this is why nothing gets fixed in GeoTools) b) do we roll our own imitation of assert (the unsupported/geometry module has an Assert class that we could rip out as a transition measure)
I am inclined to go with counting the number of asserts in GeoTools and seeing how bad the problem *is* ... the fact that an assertion is violated in a test case should tell us something. Perhaps something more important then closing a transaction. Could you let me know how to turn on asserts in maven 2? I can scope out the size of the problem next build. Then we can make an informed decision. Cheers, Jody > Jody Garnett ha scritto: >> Hi Andrea - I would like to do that ... question first. >> >> >> Is this idea anything different then the Java Assert keyword? It is a >> developer only message we are trying to reproduce here ... it has a >> documented set of procedures for how to run with asserts on and >> asserts off ... looks like a good fit. > > It does on a general point of view, not sure we can use it in practice > in our build process. Afaik we're running tests with assertions enabled, > so using assertions would mean having the build massively broken > until we fix all the places that aren't closing readers and iterators. > > Unless we want to disable assertions for a "brief" amount of time, > were brief is hard to estimate, since I would be able to work on this > on Sundays only. > > What do you think? > Cheers > Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
