ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Reilly <peter.kitt.rei...@gmail.com>
Subject Re: [tag] Re: The good ol' JUnit problem
Date Mon, 14 Nov 2005 09:48:16 GMT
Not quite,
one can use the "classloader" task as implemented
in bugzilla 28228. http://enitsys.sourceforge.net/ant-classloadertask/
Please note that this uses
protected methods on the java classes and thus may not
be future compible.

However, I do think that optional ant tasks should not
require the thirdparty jars to be placed in .ant/lib or $ANT_HOME/lib,
or require modification of ant's distribution, or require use
of protected methods...

There is a patch to allow the junit task to be loaded without refering
to the junit classes (cannot find the bugzilla number at the moment).
**I am not too sure if this is backward compatible.
I think that all *NEW* optional tasks to ant should follow that convention.

Peter

On 11/14/05, Jon Skeet <Jon.Skeet@clearswift.com> wrote:
>
> > i didn't quite catch the resolution to this. is there a
> > solution to using a stock ant distribution , without
> > modifying your target environment (ANT_HOME/lib, ~/.ant/lib,
> > etc), and using the optional tasks such as junit, scp, ftp,
> > etc? if so, can someone give an example of how to do this?
>
> No, there is no way of doing it without either modifying the environment
> or using "copies" of the tasks with different class names.
>
> Jon
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message