Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 48384 invoked from network); 25 May 2002 02:35:54 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 25 May 2002 02:35:54 -0000 Received: (qmail 18415 invoked by uid 97); 25 May 2002 02:36:00 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 18379 invoked by uid 97); 25 May 2002 02:35:59 -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 18367 invoked by uid 98); 25 May 2002 02:35:58 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <3CEEF8BB.6050106@cortexebusiness.com.au> Date: Sat, 25 May 2002 12:36:43 +1000 From: Conor MacNeill User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 X-Accept-Language: en-us, en-au MIME-Version: 1.0 To: Ant Developers List Subject: Re: [PATCH] Definer to allow types/tasks from the same jar to work References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N costinm@covalent.net wrote: > Thanks! > > Based on the feedback I got so far from Peter and Conor, > I'll leave the default behavior unchanged ( i.e. different > class loaders ). +1 > > I'll also change the name of the attribute to > 'loaderId' - and make sure this would work with a > type. +1 > > Conor - I'm not sure we should add the type. > Let me know if you think it's required, it's quite > easy to implement. I like this approach but I think perhaps we should add that in 1.6 (MAIN). > > Also for Conor - I really want to keep the magic property > for backward compatibility ( so a build.xml for 1.5 can > be used with 1.4 ). +1 There is a section in the docs where some of the magic properties are discussed - please document it there. Just FYI, in the past we have had a situation where a task could be compiled under 1.3 and 1.4 OK, but if compiled under 1.4 it would not work under 1.3. The other way was OK (compiling under 1.3 and deploying under 1.4). In this particular case, when compiled under 1.4, the resulting task class file would have references to ProjectComponent (even though there were no source references). Since this class did not exist in 1.3 it would fail. Anyway my point is that forward compatability is harder to achieve than it looks. If you are going to distribute a binary version of this task it may be necessary to compile under 1.4 rather than 1.5. You'll have to test it out, I guess. > After I commit the patch I'll update > the docs for taskdef/typedef - if you want I can only include > the new attribute and leave the magic property undocumented. Everything should be documented, IMHO. Conor -- To unsubscribe, e-mail: For additional commands, e-mail: