ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 3693] - project instance variable is null using custom task
Date Tue, 09 Oct 2001 21:11:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3693>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3693

project instance variable is null using custom task





------- Additional Comments From dan@dantanner.com  2001-10-09 14:11 -------
More info:
The project variable is only null if the <taskdef> is within a target...It 
exists if the <taskdef> is a direct child of the <project>.

I suppose this may be another effect of the classloader changes that have 
occured from 1.3 to 1.4.  We can get around this by making an <ant> call to a 
separate build file, but currently this means that you can't put a taskdef 
inside a target...in our case our target was a build-custom-tasks target which 
depended on a compile target (which ensured the custom task's class existed).

Mime
View raw message