Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Date: Tue, 8 Jun 2010 13:53:31 -0400 (EDT)
Message-Id: <201006081753.o58HrVCl002698@thor.apache.org>
From: bugzilla@apache.org
To: notifications@ant.apache.org
Subject: DO NOT REPLY [Bug 49400] Log statements in AbstractFileset can cause
 NullPointerExceptions
In-Reply-To: <bug-49400-48744@https.issues.apache.org/bugzilla/>
References: <bug-49400-48744@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=49400

J.M. (Martijn) Kruithof <jkf@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #3 from J.M. (Martijn) Kruithof <jkf@apache.org> 2010-06-08 13:53:28 EDT ---
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.

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