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 < [email protected]> 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 <[email protected]> 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.
