Hi Luke,
On May 6, 2009, at 6:38 AM, Luke Taylor wrote:
Hi all,
I've been experimenting with converting a Java multiproject build
from maven and have been very impressed so far.
One thing I've noticed is that as I progressed through my modules
(there are over 20), converting them one at a time, the process took
longer and longer as the number of dependencies on other projects
within the build increased. So even if I was running gradle within
the specific subproject directory, it would still build and test all
the dependent modules. Getting all the compile and test dependencies
worked out for each module thus took quite a long time. The fact
that the maven poms don't specify all first-level dependencies was
also a severe hindrance, admittedly.
I know that it is a lot of work when porting a Maven build. Yet I
think it is the right approach. But you can configure Gradle to behave
like Maven:
configurations.compile.transitive = true
or equivalently:
configurations {
compile.transitive = true
}
I can see why this happens, as gradle doesn't just make use of the
repository versions as maven does (if running in a subproject
directory), but I came across GRADLE-220 and was wondering what the
current plan is to enable you to just run parts of a build in
isolation.
I hopefully will commit the fix for 220 today.
Another open issue that might be of interest to you is:
http://jira.codehaus.org/browse/GRADLE-443
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
