Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.214.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F7F5D9B.2080003@apache.org>
References: 
 <CAOGo0VaeGdJ78xxTBCh0uRazbShjqQiJNkNrqyJF4je3hkCAFg@mail.gmail.com>
	<4F4A802C.3060801@kippdata.de>
	<4F7F5D9B.2080003@apache.org>
Date: Sun, 8 Apr 2012 16:12:16 +0100
Message-ID: 
 <CAOGo0VbJF8qURe+7QpOCQ7z+9Q6FhaeUtx_QLR_1a5dqgaiBXA@mail.gmail.com>
Subject: Re: Moving to Java 1.6 for a future JMeter release?
From: sebb <sebbaz@gmail.com>
To: dev@jmeter.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On 6 April 2012 22:18, Milamber <milamber@apache.org> wrote:
> Hello,
>
> No conclusion for move JMeter on target Java 1.6?
>
> With 4 votes "+", I thinks we can start to use Java 1.6 API ?

The +1 votes aren't relevant here; however the lack of -1 votes is relevant.

Since there have been no objections to the move to 1.6, we can start
using it when it becomes necessary to do so.

> Milamber
>
> Le 26/02/2012 18:55, Rainer Jung a ecrit :
>> On 26.02.2012 01:33, sebb wrote:
>>> JMeter currently targets Java 1.5 (but will of course run on Java 1.6+).
>>>
>>> At some point it might be useful to require Java 1.6 as the minimum
>>> version, as it does offer some useful enhancements.
>>>
>>> Would requiring Java 1.6 cause a problem for any JMeter users?
>>>
>>> It seems unlikely, as JMeter should be run on a different host from
>>> the system under test; i.e. the change won't require a change to
>>> existing applications.
>>>
>>> But if there are good reasons why JMeter should stick with Java 1.5
>>> rather than moving to Java 1.6, please let us know.
>>
>> +1 for 1.6.
>>
>> Rainer
>>
>