ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <dona...@apache.org>
Subject Re: <taskdef>s with nested classpath for "built-in" tasks
Date Wed, 14 Mar 2001 09:18:48 GMT
At 10:08  14/3/01 +0100, Stefan Bodewig wrote:
>The only solution I see is to either remove optional.jar from
>ANT_HOME/lib - or remove the junit task implementation from it.  Add
>some clarification to the docs - something along the lines of
>"classpath will have no effect if you define a task that is in your
>CLASSPATH and lives in a package that starts with
>org.apache.tools.ant.*".

Haven't I been saying that for ages ? - maybe not clearly I guess ;) If you
want to have optional.jar in system classpath then any other dependent jars
have to be in same classloader or parent classloader (which the system
classloader effectively doesn't have).

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*


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


Mime
View raw message