ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Loehr, Ruel" <>
Subject RE: classcast exception when attempting to use cachepath task
Date Tue, 23 Jan 2007 14:46:29 GMT
That was indeed what it was.  When I give them all the same loader ref,
it works.    I can then print out the classpath reference.  Later on
though, when I attempt to use that same classpathref it throws an error
saying that it is unknown.  I can't understand yet why it would
disappear when I attempt to use it from a different target.

What is the best practice here?  To let ivy dynamically create the
classpaths or to manually create them?

Ruel Loehr

-----Original Message-----
From: Steve Loughran [] 
Sent: Tuesday, January 23, 2007 5:47 AM
Subject: Re: classcast exception when attempting to use cachepath task

Xavier Hanin wrote:
> On 1/22/07, Loehr, Ruel <> wrote:
>> Hi.
> Hi
> I'm having a problem using the cachepath task.  I receive a class cast
>> exception when I define it.  I've researched the problem but cannot
>> not found a solution yet.
> You're problem is pretty strange, but I would bet it's a classloader
> problem. Indeed here is line 130:
>        ModuleDescriptor reference = (ModuleDescriptor)
> getResolvedDescriptor(org, module, strict);
> And the CCE indicate that the class of the object is
> DefaultModuleDescriptor, which implements ModuleDescriptor. So it's
> presumably because the ModuleDescriptor interface has not been loaded
> the same classloader as the class DefaultModuleDescriptor. How do you
> Ivy in ant? Do you use a taskdef with a special classpath, or do you
> Ivy
> in your ant lib directory? And do you call ant with some kind of
> feature, like subant or ant tasks? If it is the case try to do
> very simple (like a single build file with ivy.jar in ant lib
> only) to see if the problem comes from here or not. And if you manage
> identify the problem, please add an bug in JIRA.

If you declare types and tasks in separatate <taskdef> and <typedef> 
calls, you should force both into the same classloader instance by 
setting loaderRef="some-shared-string" in both declarations. otherwise 
ant loads them into differenct classloaders, even if the classpath is 

View raw message