title: Gradle build: does someone tried alternative build script with alternative setting.gradle?
body: <p>I am using gradle 1.4, and renamed a build.gradle to buildExpr.gradle and settings.gradle to settingExpr.gradle, both files are in the project root, and I am using following command to run gradle build.</p>
  
  <p>'gradle C:\myProject>gradle -i -b buildExpr.gradle -c settingsExpr.gradle project'</p>
  
  <p>it seems command line option '-c' is not being honored and gradle is not picking settingsExpr.gradle file, hence it is not  able to display all modules defined in settings.gradle file while executing project task.</p>
  
  <p>I am getting following log
  -------------------------------------LOG----------------------------------------------------
  C:\ASM\asm_workspace\asm71\AutoLab>gradle -i -c settingsExpr.gradle -b buildExpr.gradle project
  Starting Build
  <strong>Settings evaluated using empty settings script.</strong>
  Projects loaded. Root project using build file 'C:\ASM\asm_workspace\asm71\AutoLab\buildExpr.gradle'.
  Included projects: [root project 'AutoLab']
  Evaluating root project 'AutoLab' using build file 'C:\ASM\asm_workspace\asm71\AutoLab\buildExpr.gradle'.
  All projects evaluated.
  Selected primary task 'projects'
  Tasks to be executed: [task ':projects']
  :projects</p>
  
  <hr>
  
  <p>Root project</p>
  
  <hr>
  
  <p>Root project 'AutoLab'
  No sub-projects</p>
  
  <hr>
  
  <p>it is very strange behavior by gradle command line shows. but if I change buildExpr.gradle to build.gradle and settingsExpr.gradle to settings.gradle, it executes normally and shows all sub-modules in log</p>