You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by sebb <se...@gmail.com> on 2012/02/26 01:33:27 UTC
Moving to Java 1.6 for a future JMeter release?
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.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Milamber <mi...@apache.org>.
Le 23/11/2012 15:05, sebb a ecrit :
> On 23 November 2012 08:04, Philippe Mouawad<ph...@gmail.com> wrote:
>> Hello,
>> A new argument , it is Blocker to fix issue :
>>
>> - https://issues.apache.org/bugzilla/show_bug.cgi?id=46677
>>
>>
>> If it was to be accepted , what would be the steps:
>>
>> - Upgrade build script
Ant build script can already compiled JMeter with a Java 1.6 JDK.
But some properties / links must be update (target.java.version for example)
>> - Update docs
I can do this too if you want.
Milamber
>> - Upgrade Jenkins setup ? who can do that ?
> I can update Jenkins.
> Not sure if Gump and Buildbot will need updating, but I can probably
> do them if necessary.
>
> We would also need to add @Override tags to all interface
> implementations to avoid the warnings.
> I think that's the biggest change but Eclipse can help.
>
> There are one or two places where using Java 1.6 will allow code to be
> simplified; we can fix those as we go along.
>
>> Regards
>>
>> Philippe
>> On Mon, Sep 3, 2012 at 10:43 PM, Philippe Mouawad<
>> philippe.mouawad@gmail.com> wrote:
>>
>>> Another argument:
>>> Exception cascading on many core Java Exception (IOException, ...)
>>>
>>>
>>> On Tue, Jun 5, 2012 at 10:58 PM, Philippe Mouawad<
>>> philippe.mouawad@gmail.com> wrote:
>>>
>>>> Hello,
>>>> I see one other case where JDK6 would be nice.
>>>> When you want to use Groovy with JSR223 sampler, you have to add a
>>>> groovy-engine which is now hard to find.
>>>>
>>>> Regards
>>>> Philippe M.
>>>>
>>>>
>>>>
>>>> On Mon, Apr 23, 2012 at 3:44 PM, Philippe Mouawad<
>>>> philippe.mouawad@gmail.com> wrote:
>>>>
>>>>> Hello,
>>>>> I see one straight case in webservice sampler.
>>>>> Wsdl could be loaded in à swingworker to avoid blocking gui when wsdl
>>>>> takes some Time to load.
>>>>> I remember we had an issue on this opened 15 days ago.
>>>>> Same for drag and drop Enhancements which we workaround with more code.
>>>>> It's not critical i agree
>>>>> Regards
>>>>> Philippe
>>>>>
>>>>>
>>>>> On Sunday, April 8, 2012, sebb wrote:
>>>>>
>>>>>> On 6 April 2012 22:18, Milamber<mi...@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
>>>>>>>>
>>>>>
>>>>> --
>>>>> Cordialement.
>>>>> Philippe Mouawad.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Cordialement.
>>>> Philippe Mouawad.
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by sebb <se...@gmail.com>.
On 23 November 2012 08:04, Philippe Mouawad <ph...@gmail.com> wrote:
> Hello,
> A new argument , it is Blocker to fix issue :
>
> - https://issues.apache.org/bugzilla/show_bug.cgi?id=46677
>
>
> If it was to be accepted , what would be the steps:
>
> - Upgrade build script
> - Update docs
> - Upgrade Jenkins setup ? who can do that ?
I can update Jenkins.
Not sure if Gump and Buildbot will need updating, but I can probably
do them if necessary.
We would also need to add @Override tags to all interface
implementations to avoid the warnings.
I think that's the biggest change but Eclipse can help.
There are one or two places where using Java 1.6 will allow code to be
simplified; we can fix those as we go along.
>
> Regards
>
> Philippe
> On Mon, Sep 3, 2012 at 10:43 PM, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Another argument:
>> Exception cascading on many core Java Exception (IOException, ...)
>>
>>
>> On Tue, Jun 5, 2012 at 10:58 PM, Philippe Mouawad <
>> philippe.mouawad@gmail.com> wrote:
>>
>>> Hello,
>>> I see one other case where JDK6 would be nice.
>>> When you want to use Groovy with JSR223 sampler, you have to add a
>>> groovy-engine which is now hard to find.
>>>
>>> Regards
>>> Philippe M.
>>>
>>>
>>>
>>> On Mon, Apr 23, 2012 at 3:44 PM, Philippe Mouawad <
>>> philippe.mouawad@gmail.com> wrote:
>>>
>>>> Hello,
>>>> I see one straight case in webservice sampler.
>>>> Wsdl could be loaded in à swingworker to avoid blocking gui when wsdl
>>>> takes some Time to load.
>>>> I remember we had an issue on this opened 15 days ago.
>>>> Same for drag and drop Enhancements which we workaround with more code.
>>>> It's not critical i agree
>>>> Regards
>>>> Philippe
>>>>
>>>>
>>>> On Sunday, April 8, 2012, sebb wrote:
>>>>
>>>>> On 6 April 2012 22:18, Milamber <mi...@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
>>>>> >>
>>>>> >
>>>>>
>>>>
>>>>
>>>> --
>>>> Cordialement.
>>>> Philippe Mouawad.
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
A new argument , it is Blocker to fix issue :
- https://issues.apache.org/bugzilla/show_bug.cgi?id=46677
If it was to be accepted , what would be the steps:
- Upgrade build script
- Update docs
- Upgrade Jenkins setup ? who can do that ?
Regards
Philippe
On Mon, Sep 3, 2012 at 10:43 PM, Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:
> Another argument:
> Exception cascading on many core Java Exception (IOException, ...)
>
>
> On Tue, Jun 5, 2012 at 10:58 PM, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Hello,
>> I see one other case where JDK6 would be nice.
>> When you want to use Groovy with JSR223 sampler, you have to add a
>> groovy-engine which is now hard to find.
>>
>> Regards
>> Philippe M.
>>
>>
>>
>> On Mon, Apr 23, 2012 at 3:44 PM, Philippe Mouawad <
>> philippe.mouawad@gmail.com> wrote:
>>
>>> Hello,
>>> I see one straight case in webservice sampler.
>>> Wsdl could be loaded in à swingworker to avoid blocking gui when wsdl
>>> takes some Time to load.
>>> I remember we had an issue on this opened 15 days ago.
>>> Same for drag and drop Enhancements which we workaround with more code.
>>> It's not critical i agree
>>> Regards
>>> Philippe
>>>
>>>
>>> On Sunday, April 8, 2012, sebb wrote:
>>>
>>>> On 6 April 2012 22:18, Milamber <mi...@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
>>>> >>
>>>> >
>>>>
>>>
>>>
>>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>>
>>>
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Philippe Mouawad <ph...@gmail.com>.
Another argument:
Exception cascading on many core Java Exception (IOException, ...)
On Tue, Jun 5, 2012 at 10:58 PM, Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:
> Hello,
> I see one other case where JDK6 would be nice.
> When you want to use Groovy with JSR223 sampler, you have to add a
> groovy-engine which is now hard to find.
>
> Regards
> Philippe M.
>
>
>
> On Mon, Apr 23, 2012 at 3:44 PM, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Hello,
>> I see one straight case in webservice sampler.
>> Wsdl could be loaded in à swingworker to avoid blocking gui when wsdl
>> takes some Time to load.
>> I remember we had an issue on this opened 15 days ago.
>> Same for drag and drop Enhancements which we workaround with more code.
>> It's not critical i agree
>> Regards
>> Philippe
>>
>>
>> On Sunday, April 8, 2012, sebb wrote:
>>
>>> On 6 April 2012 22:18, Milamber <mi...@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
>>> >>
>>> >
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Philippe Mouawad <ph...@gmail.com>.
Ignore this, I am wrong
On Tue, Jun 5, 2012 at 10:58 PM, Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:
> Hello,
> I see one other case where JDK6 would be nice.
> When you want to use Groovy with JSR223 sampler, you have to add a
> groovy-engine which is now hard to find.
>
> Regards
> Philippe M.
>
>
>
> On Mon, Apr 23, 2012 at 3:44 PM, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>> Hello,
>> I see one straight case in webservice sampler.
>> Wsdl could be loaded in à swingworker to avoid blocking gui when wsdl
>> takes some Time to load.
>> I remember we had an issue on this opened 15 days ago.
>> Same for drag and drop Enhancements which we workaround with more code.
>> It's not critical i agree
>> Regards
>> Philippe
>>
>>
>> On Sunday, April 8, 2012, sebb wrote:
>>
>>> On 6 April 2012 22:18, Milamber <mi...@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
>>> >>
>>> >
>>>
>>
>>
>> --
>> Cordialement.
>> Philippe Mouawad.
>>
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
I see one other case where JDK6 would be nice.
When you want to use Groovy with JSR223 sampler, you have to add a
groovy-engine which is now hard to find.
Regards
Philippe M.
On Mon, Apr 23, 2012 at 3:44 PM, Philippe Mouawad <
philippe.mouawad@gmail.com> wrote:
> Hello,
> I see one straight case in webservice sampler.
> Wsdl could be loaded in à swingworker to avoid blocking gui when wsdl
> takes some Time to load.
> I remember we had an issue on this opened 15 days ago.
> Same for drag and drop Enhancements which we workaround with more code.
> It's not critical i agree
> Regards
> Philippe
>
>
> On Sunday, April 8, 2012, sebb wrote:
>
>> On 6 April 2012 22:18, Milamber <mi...@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
>> >>
>> >
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Philippe Mouawad <ph...@gmail.com>.
Hello,
I see one straight case in webservice sampler.
Wsdl could be loaded in à swingworker to avoid blocking gui when wsdl takes
some Time to load.
I remember we had an issue on this opened 15 days ago.
Same for drag and drop Enhancements which we workaround with more code.
It's not critical i agree
Regards
Philippe
On Sunday, April 8, 2012, sebb wrote:
> On 6 April 2012 22:18, Milamber <milamber@apache.org <javascript:;>>
> 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
> >>
> >
>
--
Cordialement.
Philippe Mouawad.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by sebb <se...@gmail.com>.
On 6 April 2012 22:18, Milamber <mi...@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
>>
>
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Milamber <mi...@apache.org>.
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 ?
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
>
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Rainer Jung <ra...@kippdata.de>.
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
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Philippe Mouawad <ph...@gmail.com>.
+1 for moving to 1.6.
On Sun, Feb 26, 2012 at 10:42 AM, Milamber <mi...@apache.org> wrote:
> Hello,
>
> I'm agree. There isn't any reason to keep Java 5 compliance (which no
> longer supported by Oracle/Sun).
>
> Milamber
>
> Le 26/02/2012 00:33, sebb a ecrit :
> > 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.
> >
> >
>
>
--
Cordialement.
Philippe Mouawad.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Milamber <mi...@apache.org>.
Hello,
I'm agree. There isn't any reason to keep Java 5 compliance (which no
longer supported by Oracle/Sun).
Milamber
Le 26/02/2012 00:33, sebb a ecrit :
> 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.
>
>
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Shay Ginsbourg <sg...@gmail.com>.
Since the automatic JAVA update process is installed alongside JVM on the
Jmeter workstations as opposed to the SUT hosts, there may actually be no
good reason to limit Jmeter to EOL JAVA versions.
Shay
On Sun, Feb 26, 2012 at 7:17 AM, Kirk Pepperdine
<ki...@gmail.com>wrote:
> 1.6 is soon to be EOL. My guess is (and we can ask Donald Smith from
> Oracle) the only thing keeping 1.6 from being EOL'ed is the lateness of the
> 1.7 and the fact that the Mac port has still not been GA'ed.
>
> Kirk
>
> On 2012-02-26, at 3:10 AM, David Brown wrote:
>
> > +1 1.6
> >
> >
> > On Sun, 2012-02-26 at 00:33 +0000, 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.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> >> For additional commands, e-mail: user-help@jmeter.apache.org
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
--
Regulatory, Medical & Performance Testing Services:
* IEC 62304 Medical Device Software Life Cycle
* IEEE 829 Software Test Documentation
* ISO 14971 Medical Device Risk Management
* FDA 21 CFR Part 11 Software Validation
* IEC 60601-1:2005 3rd ED PEMS - Medical Electrical Equipment
* End-to-end verification, validation, and testing (VV&T)
* High quality service for FDA and CE submissions
* Reliable open source free testing tools
* Optional functionality and regression testing
* Software Performance & Load Testing
* Software Testing Advanced Automation
* Medical Software Verification & Validation
* Medical Device Verification & Validation
* Medical Device Regulatory Submission
* Organizational Regulatory Qualification
Shay Ginsbourg
Regulatory & Testing Affairs Consultant
Formerly QA Manager of LoadRunner at Mercury Interactive
M.Sc. cum laude in Bio-Medical Engineering
M.Sc. in Mechanical Engineering
Work: 035185873
Mobile: 0546690915
Email: sginsbourg@gmail.com
http://il.linkedin.com/in/shayginsbourg
WWW.GINSBOURG.COM
Please consider your environmental responsibility before printing this
e-mail.
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Geoff Simmons <ge...@uplex.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 2/26/12 2:44 PM, Bruno Antunes wrote:
> Is anyone running JMeter tests using Java SE 5?
Experience suggests that it can be absolutely amazing how many people
continue to use obsolete versions of Java.
That said, I also vote +1 for requiring Java 1.6. Unless you're
developing for JMeter, then you just need the JVM to run the app, and
the only possible hindrance to an upgrade is the availability of the
newer version on your platform. Conceivably, someone's plugin might
encounter compatibility problems under a new version, but that's
unlikely and it shouldn't hold the JMeter project back.
Best,
Geoff
- --
UPLEX Systemoptimierung
Schwanenwik 24
22087 Hamburg
http://uplex.de/
Mob: +49-176-63690917
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJPSjrZAAoJEOUwvh9pJNURzkoP/0Rv8tx6vk6cYhOhB6Iz5UuS
IpVH5eqWpFcDiPQV+WZtKyFnNhArMd4j3jf4m3/zZsTvcRhMcrgbtSBKR1gg7oqn
fRBmSiI+cy7mOwxB1JhVozpj05er2lHmGrDnq+XrVm8ybko9G+QhSKPAipz3NEKS
6jqht5fvt+E9nCXuq0vrk0QnHh+Ds23o5XuRTPz83lVTh4cIvMEHrQukzlaZrHuE
Jo+6/m8TRpibMw46L9kYXddB36VJlPGzq9K72y2Pgmh38AFOMeY7XfZUeFKePi78
+XyoztxVP+IaYyInBBRHohp5C/cCXhi0b4tOey8m6UkpQyGhdtCsoZ8e/6on38+T
rQRCNwNMlkz4eEBi18qjY8OC6FWoE992Yvseiy/y5aTI5VJ5OkdxszgahvkfNGEJ
Mj3sDlrLT6wJtBob/4NUSm6R9PzAVuFCzF744JoXRo9j3NT1hb07Lo0+lWlLe644
oV2pbqhA85RnrLUCD/jjOGVIpXnJfrsso9+CPF6sBnaQARoEskEuYamP+nOVT9Sp
+b0+bfUwkgDHE7kyeRHpZCUFS42cs9HlFSeN9YbfRHUGlt7VF36ISwDDy7AFTfOw
TOBp46F642I8rfROdIQitCMEMoQ/VzABaoSL4osXKXDRYddB1GF8L1GE/bBb0/u7
u0jtrUb7Bf/aiP9UoTWd
=+jLw
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Bruno Antunes <br...@gmail.com>.
Is anyone running JMeter tests using Java SE 5?
JMeter should move to Java SE 6, and officially supported to run with Java
SE 7
--
Bruno Antunes
Software Engineer
On Sun, Feb 26, 2012 at 1:30 PM, Kirk Pepperdine
<ki...@gmail.com>wrote:
> Hi Sebb,
>
> I'm not sure what HP is up to w.r.t Java. It used to be that they took the
> Sun source, juiced it up a wee bit and.... Maybe Donald can comment, if not
> directly to the list but to either you or myself which we can repost.
>
> And Donald, before you object to the lateness comment, no, it wasn't
> Oracle's fault ;-), Oracle delivered perfectly on their projected schedule
> for which we are thankful!
>
> Regards,
> Kirk
>
> On 2012-02-26, at 2:00 PM, sebb wrote:
>
> > On 26 February 2012 05:17, Kirk Pepperdine <ki...@gmail.com>
> wrote:
> >> 1.6 is soon to be EOL. My guess is (and we can ask Donald Smith from
> Oracle) the only thing keeping 1.6 from being EOL'ed is the lateness of the
> 1.7 and the fact that the Mac port has still not been GA'ed.
> >
> > BTW, there are currently no versions of Java 7 for some other OSes,
> > including OpenVMS (HP).
> > [Not really relevant to JMeter, as it is more likely to be run on a
> > different OS]
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> > For additional commands, e-mail: user-help@jmeter.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Kirk Pepperdine <ki...@gmail.com>.
Hi Sebb,
I'm not sure what HP is up to w.r.t Java. It used to be that they took the Sun source, juiced it up a wee bit and.... Maybe Donald can comment, if not directly to the list but to either you or myself which we can repost.
And Donald, before you object to the lateness comment, no, it wasn't Oracle's fault ;-), Oracle delivered perfectly on their projected schedule for which we are thankful!
Regards,
Kirk
On 2012-02-26, at 2:00 PM, sebb wrote:
> On 26 February 2012 05:17, Kirk Pepperdine <ki...@gmail.com> wrote:
>> 1.6 is soon to be EOL. My guess is (and we can ask Donald Smith from Oracle) the only thing keeping 1.6 from being EOL'ed is the lateness of the 1.7 and the fact that the Mac port has still not been GA'ed.
>
> BTW, there are currently no versions of Java 7 for some other OSes,
> including OpenVMS (HP).
> [Not really relevant to JMeter, as it is more likely to be run on a
> different OS]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Moving to Java 1.6 for a future JMeter release?
Posted by sebb <se...@gmail.com>.
On 26 February 2012 05:17, Kirk Pepperdine <ki...@gmail.com> wrote:
> 1.6 is soon to be EOL. My guess is (and we can ask Donald Smith from Oracle) the only thing keeping 1.6 from being EOL'ed is the lateness of the 1.7 and the fact that the Mac port has still not been GA'ed.
BTW, there are currently no versions of Java 7 for some other OSes,
including OpenVMS (HP).
[Not really relevant to JMeter, as it is more likely to be run on a
different OS]
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Kirk Pepperdine <ki...@gmail.com>.
1.6 is soon to be EOL. My guess is (and we can ask Donald Smith from Oracle) the only thing keeping 1.6 from being EOL'ed is the lateness of the 1.7 and the fact that the Mac port has still not been GA'ed.
Kirk
On 2012-02-26, at 3:10 AM, David Brown wrote:
> +1 1.6
>
>
> On Sun, 2012-02-26 at 00:33 +0000, 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.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>> For additional commands, e-mail: user-help@jmeter.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Moving to Java 1.6 for a future JMeter release?
Posted by David Brown <da...@davidwbrown.name>.
+1 1.6
On Sun, 2012-02-26 at 00:33 +0000, 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.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Moving to Java 1.6 for a future JMeter release?
Posted by Adrian Speteanu <as...@gmail.com>.
+1 for java 1.6.
However what version of 1.6 remains to be seen. On some unix distributions,
on solaris, the version is not updated as often as on windows.
For me the latest stable version is ok, the upper versions of 1.6 and the
1.7 have some very interesting features.
On Sun, Feb 26, 2012 at 9:34 AM, apc <ap...@apc.kg> wrote:
> +1 for 1.6
>
> -----
> --
> Andrey Pohilko
> JP@GC Maintainer
> --
> View this message in context:
> http://jmeter.512774.n5.nabble.com/Moving-to-Java-1-6-for-a-future-JMeter-release-tp5516141p5516378.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
> For additional commands, e-mail: user-help@jmeter.apache.org
>
>
Re: Moving to Java 1.6 for a future JMeter release?
Posted by apc <ap...@apc.kg>.
+1 for 1.6
-----
--
Andrey Pohilko
JP@GC Maintainer
--
View this message in context: http://jmeter.512774.n5.nabble.com/Moving-to-Java-1-6-for-a-future-JMeter-release-tp5516141p5516378.html
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org