Hi all, the strange build errors we're experiencing on CC are sometimes caused by jalopy changing some code on the build server and getting conflicts next time an svn update is performed.
Given that a few complained about the time jalopy eats during builds, what about the following: * we disable jalopy from all modules, but we leave it configured so that you can still run it interactively with mvn jalopy:format (it just does not activate automatically) * module mantainers and developers that have reached an agreement with the module mantainer can run it before commits, if the module is supposed to be already automatically formatted, or run it in a separate commit that will be marked as "jalopy reformatting" Do you agree? 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
