On 31/03/10 5:43 AM, Hans Dockter wrote:
The last point is just an issue in the context "gradle does not
lock you in":
I'd like to have the testreports at rootProject-level with
subdirectories for
each project, so I tried:
testReportDirName = new File(rootProject.projectDir.absolutePath
+ "/reports/", project.name
<http://project.name>)
but gradle did not respect the absolute path.
Then I read in the userguide, that the testReportDir is relative
to the
reportdir, which is relative to the builddir.
Well, from my point of view this is kind of "locked in".
You are right. It is something that got introduced in the early days
and we haven't gotten around to improve this, but will do so for 1.0.
There are a couple of dirs that must be relative. This is not a good idea.
I've fixed these so that they will handle absolute paths.
Our pattern recently has been to have a single property, rather than a
read-only File property and a String name property. That is, I think we
should replace, for example
File getBuildDir()
String getBuildDirName()
void setBuildDirName(String name)
with
File getBuildDir()
void setBuildDir(Object path) // converted to a File as per
Project.file(path)
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
