Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 71337 invoked by uid 500); 8 Jun 2001 06:38:12 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 71304 invoked from network); 8 Jun 2001 06:38:10 -0000 X-Authentication-Warning: bodewig.bost.de: bodewig set sender to bodewig@apache.org using -f To: ant-dev@jakarta.apache.org Subject: Re: modifying optional task code / References: <00b301c0ef00$6400b3e0$6401a8c0@GILAMONSTER> <004601c0ef53$45f91650$6401a8c0@GILAMONSTER> <013201c0ef98$80d4c8b0$7691070f@cv.hp.com> From: Stefan Bodewig Date: 08 Jun 2001 08:38:16 +0200 In-Reply-To: "Steve Loughran"'s message of "Thu, 7 Jun 2001 14:26:20 -0700" Message-ID: Lines: 24 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Steve Loughran wrote: > One feature of the mail task is that it needs no extra jars; the > mimemail task has enough dependencies to make its use very optional, > and you cant even build it without using reflection left right and > centre. Or you don't even try to use reflection and put the implementation of the JavaMail implementation of the mail task into optional.jar > A merged task would have to do this if it wanted to be fully > backwards compatible and support build/deployments on systems > without the extra jars. Not really. Make the mail task a facade task that will try to instantiate the JavaMail implementation and fall back to the plain old version if it cannot load that class. > If the mimemail task moves to a fileset, we should pull the files > attribute. Unless we had a merged task, of course. Stefan