Sure, we could move the settings file there (we have done so already in fact). I just feel that there is still an issue here. Even when you get rid of settings.gradle, the --project-dir and --build-file options will fight in the same basic way. I'm not sure of the consequences of this fight, they might be harmless, but I know the basic underpinnings are there. This is because in StartParameters, both setProjectDir() and setBuildFile() change the current dir without consideration if the other method has been called.
On Wed, Aug 19, 2009 at 4:37 AM, Adam Murdoch <[email protected]> wrote: > > A simple solution to this problem (conceptually, at least) would be to get > rid of the settings file. Then the problem goes away. > > Any chance you could live with a workaround like moving the settings file > to <root of projects> temporarily? -- John Murph Automated Logic Research Team
