Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Today Ivy uses the classloader in which is it is loadded to load plugins. The problem of that apparoach is that the classpath definition is the reponsability of the caller, and is thus not consistent between ant, standalone and ivyDE mode.
Being able to use a custom classloader to which users could add jars in ivyconf would thus be a good improvement