On 12/03/10 8:53 PM, koevet wrote:
Hello, I have just started looking into Gradle, great great tool, I'm
finally having some fun writing build scripts.
I have a problem though, related to multi project dependencies:
I have the following project structure
-common
--util
-schema
-service
--service1
---service1-web
----build.gradle
---service1-ear
--service2
---service2-web
----build.gradle
---service2-ear
build.gradle
settings.gradle
The settings.gradle file looks like:
| include 'schema', 'common:util', 'service:service1-web',
service1-ear', 'service2-web', 'service2-ear' |
In the root build.gradle file I have a task named "*wlsdc*" that
*should* generate a bunch of classes in the build folder of any
"*-web" sub project.
When I execute "/gradle wsldc/" in the "service1-web" folder the task
generates the files in the build folder of "service2-web"! If I remove
| 'service2-web', 'service2-ear' |
from settings.gradle then the generated files are correctly placed in
"service1-web/build".
I hope that my explanation makes sense. I'm using Gradle 0.8.
Without seeing your build file, I would guess you're running into
http://jira.codehaus.org/browse/GRADLE-708, which has been fixed in trunk.
There's a few ways to work around the problem. Could you post the
snippet from your build file which shows how you add the task?
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
