Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 23420 invoked from network); 2 Jun 2002 17:46:38 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Jun 2002 17:46:38 -0000 Received: (qmail 11806 invoked by uid 97); 2 Jun 2002 17:46:28 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 11741 invoked by uid 97); 2 Jun 2002 17:46:27 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 11715 invoked by uid 98); 2 Jun 2002 17:46:26 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <009a01c20a5d$633d6740$797ba8c0@sseal.secretseal.com> From: "Hal Hildebrand $web$" To: "Ant Users List" References: <003501c2096f$c7f669f0$f0ea5c8b@manu.com> Subject: How to avoid "Trying to override old definition of task" Date: Sun, 2 Jun 2002 10:45:32 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N In 1.5 Beta 2, I still have the annoyingly prodigious output when I run my builds: Trying to override old definition of task Perhaps someone can show me how to accomplish the following without generating these messages. The build has a common include file which defines the tasks used throughout the build. The annoying message comes about when one task calls another task in the build that exists in another project. Since they are including the same common XML include file, they are all attempting to define the same task definitions. This seems like a natural thing to do for even reasonably complex builds and certainly seems in line with best practices. So the question I have is how to do this without provoking the annoying warning of Ant when this kind of pattern is used? I can get rid of the messages by modifying line 822 of Project to: MSG_VERBOSE); It would seem that when this use of includes to define common tasks throughout the build will inevitably trigger these messages because the classes will always be different. Is there something that I'm missing with respect to best practices regarding of common task definitions in multiple projects of a build? Thanks -Hal ______ All your data-base are belong to us www.hellblazer.com -- To unsubscribe, e-mail: For additional commands, e-mail: