On 26 May 2015 at 20:17, Philippe Mouawad <[email protected]> wrote: > Hi, > I think it would be over engineering. > I had previous experience with Class Loader isolation, it is rather complex > and sometimes debugging issues is really not easy. > > I think it is pretty feasible to either follow same dependencies or use > something like jarjar to embed other versions. > > @Andrei, I think it can be considered as a regression in httpmime.
Agreed. > Do we agree that if we upgrade httpmime we need to do the change, so let's > fix it. No, I think it should be fixed in httpmime. Or at least that approach should be tried first, because the cause is httpmime and fixing it there will fix it for everyone. > Regards > > > > On Tue, May 26, 2015 at 8:49 PM, Vladimir Sitnikov < > [email protected]> wrote: > >> Can we isolate "in-core" classloaders from plugin classloaders? >> >> For instance, allow a plugin use "per-plugin" class loader, so if the >> plugin author opts-in for her own classloader, then the plugin sees >> just JMeter core files and the jars from the plugin's folder. >> >> That would eliminate "we can't both keep version and upgrade" issues. >> >> Vladimir >> > > > > -- > Cordialement. > Philippe Mouawad.
