Hey, I think --build-file does not combine with --settings-file at the moment. As a workaround you can use the --project-dir instead of --build-file?
Cheers! On Mon, Jul 11, 2011 at 7:14 AM, vsajja <[email protected]> wrote: > I'm trying to set the project name as I don't want it to default to the > folder name. This can only be done through a settings.gradle file as the > name of the project is read-only. However there's a problem when I'm have > two gradle files in the same folder and want to pass in the settings file as > a command line argument. > > For example, if I have: > > projectA.gradle > projectB.gradle > settingsA.gradle (rootProject.name = 'projectA') > settingsB.gradle (rootProject.name = 'projectB') > > If I run *gradle -b projectA.gradle -c settingsA.gradle*, it doesn't pick up > the name of my project and defaults to the folder name. If I run *gradle -C > settingsA.gradle properties*, I can see the name property is set correctly. > > Any help much appreciated. > > Thanks, > Vinod > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/setting-project-name-through-settings-file-tp4573917p4573917.html > Sent from the gradle-user mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Szczepan Faber Principal engineer@gradleware Lead@mockito --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
