--- Begin Message ---
...Hi, I kind of hear, that you are discussing, what kind of appears to be
in the domain of "taskdef" and its "classpath"-attribute and how classes are
loaded? Am I wrong here?
I have some examples with what could be called "local
classpath/classloader"-use - I can make it work with the somewhat complex
Jegustator - had a chat with the author - but not with JDepend, which
requires global modification of "${ant.home}/lib"...
Something one of you care to discuss? -See two examples of mine?
Does some kind of textual explanation of "classloading in Ant X.X.X/Ant 1.6"
exist?
Regards,
Morten Sabroe Mortensen
-----Original Message-----
From: peter reilly
To: Ant Developers List
Sent: 14-08-03 10:36
Subject: Re: beating the dead Ant 1.6 horse
On Thursday 14 August 2003 06:38, Costin Manolache wrote:
> Conor MacNeill wrote:
> > The others are antlib/namespace/polymorph stuff. I'm wondering if we
can
> > get to the point where the ant optional tasks are packaged as
antlibs and
> > potentially not added to the root loader if their supporting
libraries
> > are not also available to the root loader. This would allow them to
be
> > taskdef'd in later in a build.
>
> What's the status on that ? Any decision on how to deal with the
loaders ?
> I'll have some time next week, I wanted to finish the classloader task
- is
> it still usefull ?
Most definitely.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
