Summary: | AntClassLoader Constructor fails to initialize parent classloader | ||
---|---|---|---|
Product: | Ant | Reporter: | Tim <tseigne> |
Component: | Core | Assignee: | Ant Notifications List <notifications> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | jglick, tseigne |
Priority: | P3 | ||
Version: | 1.5.2 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | other |
Description
Tim
2003-07-16 02:45:25 UTC
If you pass null, AntClassLoader uses its own ClassLoader as the parent loader. This should be the same as project.getCoreLoader(). Can you let me know what problem you are having as I'm not sure why the ClassLoader change you suggest would change anything. If you have called project.setCoreLoader(coreLoader) where coreLoader is not null but a specific loader you wish to be the parent loader then this loader however will get discarded in the call outlined below. this(null,project, classpath, parentFirst); We are using Ant like a workflow engine inside an app-server and so we need certain things that we have from the appservers classloader available in ant so I need to pass appservers classloader into ant I am doing this by setting it in the project. Hope this helps a bit? Tim See also bug #30161 which could be seen as a by-product of this. |