ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Jackson" <>
Subject Re: Classloader problems
Date Fri, 08 Jun 2007 12:37:19 GMT
> Initially I was thinking of using a separate classloader for
> ant tasks/types (I cannot find the e-mail or bugzilla entry),
> but currently I do not think that this is necessary as:
>    - I do not think that more 3th class dependent optional tasks
>      will be added to ant core (they will be added as antlibs)
>      (we will have jvm dependent tasks) This means that
>      there is a relatively small number of optional tasks that need to
>      be fixed.

True, the future of optional tasks is probably antlib based.

> The problems I have with this is that:
>   1) it uses an undocumented and non-public method in a sun implementation
>       - this may change in future releases and the method might not exist
>        in non-sun implementations of the JVM.

Ah, I didn't know this as I haven't looked at the source code.

>   2) when ant is used in a IDE, in specific netbeans, the project classloader is
>       kept from build to build. So modifiing the project classloader may have
>       strange side effects in later builds on unrelated projects.

Yes that's also a problem, so two strikes.

> so I believe cl:classloader should be supported as an optional antlib.
> In my build
> system at work, I use it for handling a large number of classloading
> issues - for example junit with axis and cobutura.

Thanks for pointing me to it as it fixed my problem perfectly.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message