I think that may be the same bug as An issue with combining --project-dir and --settings-file or --build-file options<http://jira.codehaus.org/browse/GRADLE-604>. I recall the issue being something about the --build-file and --settings-file options both implicitly set the project dir. If your build.gradle and settings.gradle aren't in the same directories, that might be the problem.
On Fri, Apr 9, 2010 at 8:10 AM, Rene Groeschke <[email protected]> wrote: > hi there, > on my hudson i configured a multiproject build job which uses a custom > name for a build file and a custom name for a settings file. > > when starting the build via: > > gradle -b /absolutePathTo/bsp.build.gradle -c > /absolutePathTo/bsp.settings.gradle test uploadArchives > > gradle quits and tells me, that test and uploadArchives are unknown tasks. > renaming my files to the default values and running "gradle test > UploadArchives" works fine. this is a bug isn't it? > > regards, > René > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- John Murph Automated Logic Research Team
