JerodLass wrote:
I also tried adding the clientModule from the configurations closure, but I
still can't seem to get it. Anybody know how to translate the included
gradle <0.6 code to 0.6?
JerodLass wrote:
More gradle 0.6 questions...
I currently use a custom ant task for deploying ejbs (it's very clunky),
and I was wondering how the following code will need to be different in
gradle 0.6:
project.dependencies{
addConfiguration('wsanttasks')
clientModule(['wsanttasks'], "com.ibm.websphere:runtime:6.1.0")
}
This should work:
configurations {
wsanttasks
}
depedencies {
wsanttasks module("com.ibm.websphere:runtime:6.1.0")
}
Section 21.2.3 in the user guide has another example:
http://www.gradle.org/0.6/docs/userguide/dependency_management.html
I have tried splitting the addConfiguration off to a "configurations"
closure according to the 0.6 breaking changes spec, but then I get
complaints about the clientModule line:
A problem occurred evaluating project ':projectEJB'.
Cause: No signature of method:
org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.clientModule()
is applicable for argument types: (java.util.ArrayList, java.lang.String)
values: {["wsanttasks"], "com.ibm.websphere:runtime:6.1.0"}
How can I get the jar as a dependency in 0.6?
Thank you for any help
Jerod
