ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 49400] Log statements in AbstractFileset can cause NullPointerExceptions
Date Tue, 08 Jun 2010 18:07:24 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=49400

gavares@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WONTFIX                     |INVALID

--- Comment #4 from gavares@gmail.com 2010-06-08 14:07:22 EDT ---
 It seems like a bad thing for logging statements to cause NPE's or, more
generally, for logging statements to halt the execution of code. 

This isn't a significant problem, and I admit that I'm using the and tasks
outside the scope of their original intent so perhaps this shouldn't be a
bug.(In reply to comment #3)
> Setting the project is an explicit step in the lifecycle of each task,
> therefore you should always set the project instance, also when using ant task
> programatically, note that this is also valid for the Location and Target,
> these items are explicitly stated in the manual.
> These can be set using setProject, setLocation and setOwningTarget.
> 
> The workaround you describe actually solves a part of the bug in your code, in
> such way that you are not hitting a bug anymore. Though the code still does not
> obey the lifecycle of the task.

Fair enough, although I would like to make the point that it seems like a bad
thing for logging statements to cause NPE's or, more generally, for logging
statements to halt the execution of code. 

This isn't a significant problem, and I admit that I'm using the and tasks
outside the scope of their original intent so perhaps this sh0ouldn't be a bug.

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

Mime
View raw message