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
Hi Hans,
Thanks for that solution. It works fine and publishes both artifacts.
However, it appears that the new Jar task is including all the classes
found in 'classesDir' as well as 'servicesFacadeClassesDir' (See task
below:)
task jarServiceFacade(type: Jar, dependsOn: compileServiceFacade) {
