Re: JMeter project structure and IDEs support

2017-07-08 Thread Emilian Bold
Could we use this opportunity to remove the junit/test.jar sample, related Maven pom.xml, ant task and perhaps the src/junit/test and src/junit/woolfel folders entirely? --emi On Sat, Jul 8, 2017 at 11:36 AM, Philippe Mouawad wrote: > Hello Emilian, > I agree with

Re: Build failed in Jenkins: JMeter Windows #663

2017-07-08 Thread Felix Schumacher
Am 8. Juli 2017 11:05:14 MESZ schrieb Philippe Mouawad : >Hi Felix, >There is something weird, as the request has a header to get only a >range >of bytes from 0-7000. >Do you think returned header have changed ? My guess is, that the headers are changing depending

Re: Build failed in Jenkins: JMeter Windows #663

2017-07-08 Thread Philippe Mouawad
Hi Felix, There is something weird, as the request has a header to get only a range of bytes from 0-7000. Do you think returned header have changed ? Thanks On Sat, Jul 8, 2017 at 11:03 AM, Felix Schumacher < felix.schumac...@internetallee.de> wrote: > Seems like the length of the start page

Re: Build failed in Jenkins: JMeter Windows #663

2017-07-08 Thread Felix Schumacher
Seems like the length of the start page changed back again :( Felix Am 8. Juli 2017 10:49:43 MESZ schrieb Apache Jenkins Server : >See > > >-- >[...truncated

Build failed in Jenkins: JMeter Windows #663

2017-07-08 Thread Apache Jenkins Server
See -- [...truncated 140.76 KB...] JSA-CheckResponseTimeHigherThan5s false false '. Target 'batch_scripts' failed with message 'The following error occurred while

buildbot failure in on jmeter-trunk

2017-07-08 Thread buildbot
The Buildbot has detected a new failure on builder jmeter-trunk while building . Full details are available at: https://ci.apache.org/builders/jmeter-trunk/builds/2784 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: bb_slave1_ubuntu Build Reason: The AnyBranchScheduler

Re: JMeter project structure and IDEs support

2017-07-08 Thread Philippe Mouawad
On Sat, Jul 8, 2017 at 9:05 AM, Emilian Bold wrote: > Q1: Maven artifact and group IDs? > > Currently I see in res/maven some basic Maven poms for central > deployment. These use the org.apache.jmeter groupId and > ApacheJMeter_parent, ApacheJMeter_http, ApacheJMeter_core

Re: JMeter project structure and IDEs support

2017-07-08 Thread Emilian Bold
Q1: Maven artifact and group IDs? Currently I see in res/maven some basic Maven poms for central deployment. These use the org.apache.jmeter groupId and ApacheJMeter_parent, ApacheJMeter_http, ApacheJMeter_core artifact Ids The groupId org.apache.jmeter is fine to me but the artifactID look odd.

Re: JMeter project structure and IDEs support

2017-07-08 Thread Vladimir Sitnikov
Philippe>The decision for no maven in project was due to the fact that nobody had time to work on it and as project has a lot of other work needed, we wanted to put efforts in other fields. Oh, really? What about moving files around in order to better follow "default maven convention"?

Re: JMeter project structure and IDEs support

2017-07-08 Thread Emilian Bold
What customization is needed? As of now I'm able to build JMeter (components, core, functions, jorphan, protocol/*) and with a little tweak run it as-is from NetBeans. One separate aspect is that I see the canonical source is under Subversion. So even if I make a Git patch (or pull request), all

Re: JMeter project structure and IDEs support

2017-07-08 Thread Philippe Mouawad
Hello, The decision for no maven in project was due to the fact that nobody had time to work on it and as project has a lot of other work needed, we wanted to put efforts in other fields. also project may be hard to mavenize knowing all the customization needed. But if there is a volunteer ,