Return-Path: 
 <dev-return-54222-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 9485 invoked from network); 8 Jan 2004 14:44:51 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 8 Jan 2004 14:44:51 -0000
Received: (qmail 53362 invoked by uid 500); 8 Jan 2004 14:43:55 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 53333 invoked by uid 500); 8 Jan 2004 14:43:55 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 53296 invoked from network); 8 Jan 2004 14:43:55 -0000
Received: from unknown (HELO exchange.sun.com) (192.18.33.10)
  by daedalus.apache.org with SMTP; 8 Jan 2004 14:43:55 -0000
Received: (qmail 25838 invoked by uid 50); 8 Jan 2004 14:44:01 -0000
Date: 8 Jan 2004 14:44:01 -0000
Message-ID: <20040108144401.25837.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 25982]  -
    empty include task inside javac causes NullPointerException
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

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=25982>.
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=25982

empty include task inside javac causes NullPointerException





------- Additional Comments From ddevienne@lgc.com  2004-01-08 14:44 -------
I'm not sure to silently ignore the <include/> is the best approach. Shouldn't 
the build barf instead, complaining about the incomplete definition of the 
<include>!?!?!? Is this possible? --DD

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