jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <>
Subject Re: JMeter : Migrate to Java8
Date Fri, 05 Aug 2016 21:15:42 GMT
I tend to follow Vladimir's reasoning on this.

Next release would support Java7 , I suppose it would be released around
september (which is more than 4 month after 3.0), based on this speed,
Java8 would concern a release made on january or february.

I believe maintaining a new branch for Java8 is a bit too much work.
We already have a lot of work and we're short of resources already, so I
will personally find it very hard to merge the branches knowing furthermore
we are using SVN and not GIT which would make this a bit more easier (But I
don't want to start again the debate on git :-) ).

In my opinion migration to Java8 doesn't have to immediately migrate
everything to the new syntax, it should be done when it concerns a new
feature or improves drastically things.

Besides, maybe we should have some rules of developments with Java8
features like lambda or streams.
I found this blog interesting on this:

Philippe M

On Thu, Aug 4, 2016 at 10:27 PM, Felix Schumacher <felix.schumacher@> wrote:

> Am 03.08.2016 um 21:34 schrieb Philippe Mouawad:
>> Hello,
>> What do you think of moving next major JMeter release 3.1 or 4 to Java 8,
>> not the next bugfix release.
>> +1 for me as :
>>     - lot of libraries are dropping Java7 compat
>>     - lambda, streams,nio2
>> Java 7 is EOL since April 2015 (
> Oracle jdk 7 is eol. There is still openjdk. I don't think that has
> reached eol yet.
> I think we should wait a bit longer before dropping java 7 support, or
> maybe take milamber's approach of supporting two branches.
> Regards,
>  Felix

Philippe Mouawad.

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