: The build does need an overhaul - there are some problems with it that I : know about - but it's not as simple as reviewing the dependencies you : mentioned - there are also implicit dependencies that are derived from : configurations dependencies, source sets, etc.
Fair -- I was mainly just wondering if you (or anyone) knew/remembered off the top of your head something that had changed in the "architecture" of our gradle deps on the main branch (since this problem doesn't sem to affect branch_9x, eventhough it also uses the same version of gradle) : in whatever order". So you may be better off setting up an alias in bash to : run gradlew clean && gradlew xyz in sequence... Or - better yet - not run : gradlew clean at all - the incremental build should work fine. Yeah, it's mainly something I do when switching branches -- but also out of muscle memory. Maybe we should add an 'afterEvaluate' hook to complain if people try to combine "clean" with other tasks on the command line? :) -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
