Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Classpath issues
Date: Tue, 30 Nov 2004 14:53:04 +0200
Message-ID: <E940C401FF44FB42ABAE1F1CB434644320C0B8@tmexch1.telmap.corp>
Thread-Topic: Classpath issues
thread-index: AcTS6pxtmES9kW2aQAW4XrIQiNZ0PQD8Cr/A
From: "Omry Yadan" <omry@telmap.com>
To: "Ant Developers List" <dev@ant.apache.org>

I can specify the classpath of user tasks when I define them.
This makes the build more portable, because I can include the required
jars with it, and have a relative classpath in the taskdef.
Can I somehow do the same for system tasks with external dependencies?
Suppose I want to use the mail task which depends on mail.jar etc.
I do not want to put mail.jar in the ant lib path, because it means
anyone else who would want to use my build need to do the same.
I would rather add it to a lib directory under the build.xml directory,
and have the build.xml reference it, like it does with my user tasks.
Can it be done?

	Omry.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org