On 3/16/07, Jakob Færch <[EMAIL PROTECTED]> wrote:
I'm developing an Eclipse plugin which runs ant build by invoking Eclipse's AntRunner class. This plugin co-exists with the IvyDE Eclipse-plugin. I've been getting classloading errors from commons-logging (the IvyDE invocation of commons-httpclient triggers the loading of commons-logging Log class, which compains about an invalid classloader hierarchi exhibiting two visible Log classes). I solved the error by removing the library version of commons-logging in the IvyDE-plugin and replacing it with a dependency of the org.apache.commons_logging plugin included which is included with Eclipse 3.2.1 - and most other versions, I believe. I have a patch file outlining the change - should I create a Jira issue to do the further discussions?
Yes, commons-logging is often the source of problems in shared environments where modules co exist in separate classloaders. Opening a JIRA issue for this would be fine if JIRA for IvyDE was migrated, but it's still not the case (should happen next week I hope :-)) So for the moment I guess the mailing list is fine. OTOH, to include your patch we would need to know if it works also with eclipse 3.1, so it would help us if you can test with eclipse 3.1 too. - Xavier Kindly,
Jakob
