I think for faster fix: - it should be fixed in jmeter as anyway we use a deprecrated method (probably removed in future version of httpmime). We can see it as a workaround but this approach has been taken in the past for httpclient bugs.
- report a bug to httpmime Otherwise we slow down the fix for our project , seen from customer perspective of jmeter , the issue is in jmeter. That's the important thing for me. If workaround was big or ugly I would not do it, but here it's clean(use up to date method) and fast and Andrei analyzed it already. Regards On Wednesday, May 27, 2015, sebb <[email protected]> wrote: > On 26 May 2015 at 20:17, Philippe Mouawad <[email protected] > <javascript:;>> 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] <javascript:;>> 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. > -- Cordialement. Philippe Mouawad.
