You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Milamber <mi...@apache.org> on 2012/04/06 23:18:19 UTC

Re: Moving to Java 1.6 for a future JMeter release?

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 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
>>
>