"ant precommit" will check if the source tree is "dirty" (i.e. contains files not in source control) and stop with a failure if so. I find that rather annoying since I've usually got a variety of .patch files and IDE config changes. What is the rationale behind this check? How do people usually deal with it? Perhaps if I do my real development on another checkout (git based), I could then patch on the svn one for the commit. Pretty annoying though, and the 4x port is yet another step. There sure is a lot of burden to getting commits in. I no longer care to improve little javadoc and typo stuff.
~ David ----- Author: http://www.packtpub.com/apache-solr-3-enterprise-search-server/book -- View this message in context: http://lucene.472066.n3.nabble.com/ant-precommit-annoyed-with-checkout-is-dirty-tp4022362.html Sent from the Lucene - Java Developer mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
