Jody, I'm not sure what you're saying, but running jalopy (or anything that mangles the code) isnt a very good idea.
Running Jalopy kills history -- and makes branch-to-branch maintainance difficult. I had to waste a good chunk of a day merging changes in StreamingRenderer.java from 2.1.x to trunk (and back) because someone ran something that changed almost every line of code in the class. Chris ran jalopy on something in Geoserver and I just gave up trying to figure out what had changed (unfortunately his jalopy commit also had code changes in it). I'm FIRMLY -1 ; unless someone can argue that those two applications of jalopy-like stuff will actually save more than a days of someone's time (+ extra time for how frustrating & futile it is to sort through 10,000 changes). And this is *just* one java file. Running it for 3,000 files better save 10 people years! dave ---------------------------------------------------------- This mail sent through IMP: https://webmail.limegroup.com/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
