Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 23410 invoked from network); 21 Dec 2001 17:37:09 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 21 Dec 2001 17:37:09 -0000 Received: (qmail 23335 invoked by uid 97); 21 Dec 2001 15:30:46 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 23292 invoked by uid 97); 21 Dec 2001 15:30:44 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 23244 invoked from network); 21 Dec 2001 15:30:44 -0000 From: "Igor Shkatov" To: "Ant Developers List" Subject: Available task and the class methods Date: Fri, 21 Dec 2001 18:30:41 +0300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I think, that there is a sense to add the methodname attribute to the Available task to have possibility to check the existence of the specific method in the class. In my case it is required to have the possibility to resolve the version incompatibility before the actual build/test/deployment process occurs. Is there anyone who thought about this? regards, Igor -- To unsubscribe, e-mail: For additional commands, e-mail: