On Thu, Jul 19, 2012 at 2:11 PM, Dawid Weiss <[email protected]> wrote: >> it breaks my ide completely and causes the project to fail. clean > > Are you talking about Eclipse? I don't know, I've just done the above > and nothing breaks for me.
The editor appears to work at first: But it definitely breaks as soon as it needs to compile anything (which happens constantly as you type), or god forbid refresh the project for any reason (as those jars are now deleted). > >> often times i just call clean before i rerun a single test or >> something, its just a habit > > That's a good habit. And exactly the same reason for syncing the jars > used for compilation and execution with the ivy files -- so that you > don't run with stuff you're not supposed to run with? I dont svn up arbitrarily or often for any reason. when i am working on something, i work with that revision until i'm happy. then i svn up and merge any changes from trunk (when i do svn up, i clean-jars). I've never had any issues with stale jars... on the other hand my IDE is broken. > Backtracking a bit -- ideally we should use a classpath built directly > from those ivy files... then it wouldn't matter. But then things would > get complicated for other IDEs anyway (because not all of them support > ivy as far as I can tell?). I agree with what you say there. My point is that its now totally broken: 1. i dont like top level targets that do different shit than the ones under lucene/ and solr/. This makes the build totally inconsistent and confusing. 2. i dont like targets like test calling unrelated targets (add test-all or precommit if you want this), or clean calling unrelated shit for me. add 'clean-all' if you want this! 3. I don't like targets that delete anything except whats in my build/ directory. The other stuff could be important: to me or to my IDE. So please, please, please, lets remove this dependency. -- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
