It compiled and I could run the build, but I just started trying to actually
run the wsejbdeploy ant task and I get an error:
No signature of method:
org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.antpath()
is applicable for argument types: (java.lang.String) values:
If you have the classpath you want to reference in a configuration called
wsanttasks, then try changing:
taskdef(name: wsejbdeploy,
classname:com.ibm.websphere.ant.tasks.WsEjbDeploy,
classpath:project.dependencies.antpath(wsanttasks))
to
taskdef(name: wsejbdeploy,
On Jun 22, 2009, at 8:28 PM, JerodLass wrote:
It compiled and I could run the build, but I just started trying to
actually
run the wsejbdeploy ant task and I get an error:
No signature of method:
org
.gradle
.api
.internal
.artifacts.dsl.dependencies.DefaultDependencyHandler.antpath()
filed: http://jira.codehaus.org/browse/GRADLE-527
I have now built my first ear with gradle 0.6.1! Still a lot to do in
updating all gradle files in all projects, but I can now use gradle again.
Are there any big breaking changes in the DSL in upcoming releases? I'm
trying to decide if I
Any idea why
project.configurations{
wsanttasks
}
project.dependencies{
wsanttasks module(com.ibm.websphere:runtime:6.1.0)
}
throws a nullpointerexception on the module line when I declare it in a
plugin?
hdockter wrote:
On Jun 16, 2009, at 2:58 PM, JerodLass wrote:
snip
On Jun 17, 2009, at 3:38 PM, JerodLass wrote:
Any idea why
project.configurations{
wsanttasks
}
project.dependencies{
wsanttasks module(com.ibm.websphere:runtime:6.1.0)
}
throws a nullpointerexception on the module line when I declare it
in a
plugin?
It would also throw a NPE
Thanks, that worked. I don't have a good answer as to why I do that, but it's
for using the ant task WsEjbDeploy. I declare the module and then, later, I
refer to the configuration when I execute the task and it finds the jar.
It's something I have been using for several gradle releases.
I'm
I am now getting a nullpointerexception from the line wsanttasks
module(com.ibm.websphere:runtime:6.1.0) even though wsanttasks is
declared as you described just before it. Does it make a difference that
this is happening inside a plugin class? Also, what's the best way to get
some meaningful
On Jun 16, 2009, at 2:58 PM, JerodLass wrote:
snip
Thanks again, and keep an eye on me if you will because I will
probably run
into more problems with the DSL update. For example, I changed my
testCompile dependencies to compileTests dependencies because of the
breaking changes document,
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
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
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')
12 matches
Mail list logo
