Hi Hans,
Thanks a lot for your input. I much prefer the approach of specifying
your compile dependencies explicitly. It was also (ahem!) educational to
find out what some of them actually were :).
That's great news about the fix for GR-220, as that was slowing me up
quite a bit.
I am also pretty interested in pom generation for third party use, so I
will keep an eye on that other issue. It's also quite important that I
can mark dependencies in the generated pom as being optional. Is it
possible to do that at the moment?
Thanks,
Luke.
On 6/5/09 16:17, Hans Dockter wrote:
Hi Luke,
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 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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
