Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 40111 invoked by uid 500); 13 Mar 2001 23:21:56 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 40041 invoked from network); 13 Mar 2001 23:21:53 -0000 Date: Tue, 13 Mar 2001 17:23:24 -0600 From: Chris Stillwell Subject: Problem with includesfile in jar task. In-reply-to: <000d01c0a8a7$850eac30$585124a6@rcc05335.wcomnet.com> To: ant-user@jakarta.apache.org Message-id: <004301c0ac14$997ca4e0$585124a6@rcc05335.wcomnet.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3155.0 X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N I noticed that if a filename within the file specified by the includesfile attribute contains any trailing blanks, then the file is not included in the jar and no errors are indicated. I can easily fix my file, but I would think that whichever method is reading in these file patterns would do a trim to truncate trailing blanks. I would also like to know if it is possible to have the jar task fail if a file is not found and can't be loaded. The whenempty attribute should fail when the entire jar is empty, but what about when the jar is missing some required piece(s). Chris Stillwell