No problem. I suspect this change I made will likely be pretty solid since before, I just assumed I was using Maven's URLClassloader. Since I now am creating my own URLClassloader and stuffing it with the compile-time dependencies, I think it will stick. In any case, it works good now, and if I need to update yet again, it should not be a problem. But I suspect my injecting my own classloader will be a permafix.
Thanks for your response on this, Brett. Jeff Brett Porter wrote: > If 2.0 -> 2.0.1 broke a plugin, then I expect we need to fix that. > > There are a few issues with classloaders floating around WRT plugins. > We'll sort them all out in the core, hopefully. > > - Brett > > Jeff Genender wrote: >> Can you elaborate? It would be nice to know if there will be more >> classloader fun coming down ;-) >> >> Brett Porter wrote: >> >>> I think we better ensure the old one works again in 2.0.2. There is an >>> open issue. >>> >>> - Brett >>> >>> Jeff Genender wrote: >>> >>>> I had reports about the jspc plugin not working in maven 2.0.1. I >>>> upgraded to maven 2.0.1 and sure enough it broke the jspc plugin due to >>>> a change in the maven classloaders. I fixed the plugin to make a >>>> URLClassloader and put it in the classloading chain and all works again. >>>> So if you have encountered this problem, please update. >>>> >>>> Jeff >>>> >>>> >>>> >>
