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 38458] - [PATCH] NullPointerException thrown in Task.log() if setProject() has not been called
Date Thu, 02 Feb 2006 05:02:09 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38458>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38458





------- Additional Comments From gudnabrsam@yahoo.com  2006-02-02 06:02 -------
(In reply to comment #5)
> If that is the case, that would ideally be enforced in the constructor. 
Perhaps
> the constructor could create a "default" project in the project field to 
ensure
> the Task always has a project associated with it, for these kind of cases?

Hmm... at first I was like, what?  But if there were a static 
Project.DEFAULT_INSTANCE Project, whose only properties were System properties, 
etc... hmmm...

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message