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 getting a funny error now. It applies all of the plugins, which is
good, but now on the line:
project.libs.archiveTasks.each {bundle ->
I get an error:
Execution failed for task ':projectModule:libs'.
Cause: Could not find property 'archiveTasks' on task ':projectModule:libs'.
I still see this in the userguide in example 24.59. Is there a new way to
do something with all archives?
hdockter wrote:
>
>
> 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 when you do it like this in the build script.
>
> If you do: wsanttasks module("com.ibm.websphere:runtime:6.1.0") {}
> everything works. What is your reason for using a module if there are
> no dependencies? Why not saying for example:
>
> wsanttasks "com.ibm.websphere:runtime:6....@jar"
>
> Anyway, Gradle should not throw an NPE, so we will fix this.
>
> - Hans
>
> --
> Hans Dockter
> Gradle Project Manager
> http://www.gradle.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
>
--
View this message in context:
http://www.nabble.com/Client-module-for-custom-ant-tasks-tp23983465p24075403.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
