gt; loader straddle and two copies of a critical interface in two class
> loaders.
>
> And, indeed, a bit of poking around, shows that (a) Velocity uses the
> thread context class loader to load the resource manager, and (b) that
> was set to some Realm or another, but not the one i
and two copies of a critical interface in two class
loaders.
And, indeed, a bit of poking around, shows that (a) Velocity uses the
thread context class loader to load the resource manager, and (b) that
was set to some Realm or another, but not the one into which the
plugin itself had been loaded. So
Subject says it all. Here is the patch.
Index:
maven-plugins/hibernate/src/main/org/apache/maven/hibernate/beans/SchemaExportBean.java
===
RCS file:
/home/cvspublic/maven-plugins/hibernate/src/main/org/apache/maven/hibernate/beans/
Hi,
I have a question regarding line #445 in PluginManager.java. It sets the
context class loader to null. For some reason that I can't grasp at the
moment it does not cause breakage when Maven is being run from the
command line. While running under Eclipse's debugger however, this
causes the com
