If one uses a context.xml with a <loader> element to specify the class loader implementation to use with the tomcat7:run goal, this causes Tomcat to override the WebAppLoader carefully created by the plugin, without the
benefit of a properly configured class path.
The attached patch adds a <classLoaderClass> property to configure which class loader implementation to use. This is probably of limited utility as most classes will be loaded by the parent classloader anyway.
|Fix Version/s||2.0 [ 12319450 ]|
|Component/s||tomcat6 [ 12316300 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|1h 49m||1||Olivier Lamy (*$^¨%`£)||13/Apr/12 11:05|