jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <>
Subject Re: [GitHub] jmeter issue #221: Bug 59934
Date Wed, 10 Aug 2016 21:25:19 GMT
Thanks Vladimir, I am aware of that :-)
Could you comment on my thread.

After further thinking, I don't see why we could not upgrade to Java 8 AND
use guava.

Besides, I think it would be nice to be reactive on the project and
sometimes try things and maybe remove them afterwards.

Anyway, currently in trunk we have a feature (CSS Parsing caching) which
has an issue, if we want to release a 3.1, we need to find a solution.
There is a working PR that introduces Guava (which is largely used so I
suppose it's not bad ) , why not take it as is , fix the problem and if you
want write some note that guava introduction is "experimental" and nobody
should rely on it being in JMeter.

On Wed, Aug 10, 2016 at 11:08 PM, Vladimir Sitnikov <> wrote:

> Philippe>    I'll wait 2 more days for reaction on guava subject.
> -1 for Guava from me.
> I would rather speedup migration to java 8.
> Vladimir

Philippe Mouawad.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message