Re: Approach for Dropping LogKit in favor of Apache Log4J2 + SLF4J

2016-03-29 Thread Philippe Mouawad
Hello Sebb,
No problem for me to follow your approach.
Note that by doing this we would keep logkit and all the current feature
but just drop references to LogKit classes from all JMeter classes except
the one where configuration is used.

So it will anyway ease the migration.

Regards

On Mon, Mar 28, 2016 at 3:33 PM, sebb  wrote:

> On 27 March 2016 at 20:00, Philippe Mouawad 
> wrote:
> > Hello,
> > Just for information , within fix of :
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=59240
> >
> > I introduced an slf4j adapter for Logkit.
> > It was not for this subject particularly but more because some very
> > interesting 3rd party logs were dropped by Nop impl (ph-css in this case
> > but it's for every 3rd party logging through slf4j).
> >
> > But thinking about it, a way to move forward is to replace now
> everywhere:
> >  private static final Logger LOG = LoggingManager.getLoggerForClass();
> >
> > by :
> >   private static final Logger LOG = LoggerFactory.getLogger
> > (.class);
>
> No; that is error-prone, tedious to do and unnecessary.
>
> If we really are going to drop the Avalon logger then the obvious way
> to do this is to create a new version of getLoggerForClass() that
> returns the correct Logger.
>
> But as I recall no one has addressed the issues I raised regarding
> loss of functionality.
>
>
> > Regards
> > Philippe
> >
> >
> >
> > On Tue, Jan 5, 2016 at 11:38 AM, sebb  wrote:
> >
> >> On 3 January 2016 at 15:40, Philippe Mouawad <
> philippe.moua...@gmail.com>
> >> wrote:
> >> > Hello,
> >> > I am writing this message to have your opinion on the approach we
> should
> >> > follow.
> >>
> >> This assumes that we are agreed on replacing logging.
> >> I still think this is unnecessary work, and there is a lot to do.
> >>
> >> In any case, I think the work needs to be done in a branch so we can
> >> see how it will work in practise.
> >>
> >> > Current situation:
> >> >
> >> >- log configuration is done in jmeter.properties through:
> >> >   - log_format
> >> >   - log_format_type
> >> >   - log_level.[package_name].[classname]=[PRIORITY_LEVEL]
> >> >   - log_file.[category]=[filename]
> >> >   - log_file=jmeter.log
> >> >   - log_config=logkit.xml
> >> >
> >> >
> >> > I see 2 ways to proceed in implementation:
> >> >
> >> > COMMON PART:
> >> >
> >> >- We keep LoggingManager as is for third party plugins
> >> >- We create a LogTarget implementation that uses SLF4J to make all
> >> >current logging still work.
> >> >- Only this implementation will still use LogKit
> >> >- In next version of JMeter will will drop definitely
> >> >LogKit+Excalibur+Avalon
> >> >
> >> >
> >> > *APPROACH 1:*
> >> > Recode what currently exists for LogKit for Log4j2:
> >> >
> >> >- We create a new class to initialize logging based on Log4j2 and
> >> follow
> >> >one of these approaches:
> >> >   - https://logging.apache.org/log4j/2.x/manual/customconfig.html
> >> >- From my understanding , we should create a custom
> >> >CustomConfigurationFactory that takes Properties as Constructor
> >> passed in
> >> >JMeterUtils#initLogging
> >> >
> >> >
> >> >
> >> > *APPROACH 2:*
> >> > We drop what currently exists and just initialize it simply with a
> Log4j2
> >> > configuration file, we only keep:
> >> >
> >> >- log_file=jmeter.log as it is used by -j command line option
> >> >- log_config=log4j2.xml to configure the logging
> >>
> >> This appears to ignore one of the most useful parts of the config
> >> which allows one to configure logging separately for different
> >> packages and classes.
> >> It is also used by the JMeter menu item Help/Enable|Disable debug
> >>
> >> >
> >> > My opinion is that we should stick to standard mechanism of Log4j2
> that
> >> is
> >> > largelly documented and known and reduce as much as possible any
> custom
> >> > configuration in JMeter.
> >>
> >> Where is it documented how to enable/disable debug for a specific class?
> >>
> >> > This of course breaks backward compatibility but version numbering
> will
> >> be
> >> > explicit about it as long as the release notes.
> >> > Regards
> >> > Philippe M.
> >> > @philmdot
> >>
> >
> >
> >
> > --
> > Cordialement.
> > Philippe Mouawad.
>



-- 
Cordialement.
Philippe Mouawad.


Re: [VOTE] new logo for JMeter 3.0

2016-03-29 Thread Philippe Mouawad
Hi Felix,
When do you plan to commit the new logo so that it's used by JMeter site
and application ?
Thanks
Regards

On Thu, Mar 24, 2016 at 12:10 AM, Milamber  wrote:

>
> Yes that's would be a good choice for update/refresh the JMeter identity
> design.
>
> Milamber
>
>
> On 23/03/2016 22:31, sebb wrote:
>
>> Agreed, let's just go with 6.
>> Most people seem happy with it; I don't think anyone is against it.
>>
>> On 23 March 2016 at 19:36, Philippe Mouawad 
>> wrote:
>>
>>> Thanks Felix.
>>> Looks fair to me.
>>>
>>> Regards
>>>
>>> On Wednesday, March 23, 2016, Felix Schumacher <
>>> felix.schumac...@internetallee.de> wrote:
>>>
>>> Am 23.03.2016 um 15:29 schrieb Philippe Mouawad:

 Hello,
> Anybody computed the results ?
>
> If every mail counts as a vote (NaveenKumar sent his vote twice and I
 counted it only once, sebb gave two votes with no preference, so I
 counted
 both :) then we have two winners 3 and 6.

 If I take the preferences into account (first counts as two votes,
 second
 as one (again sebb counts both times as two)) 6 wins.

 The same is true if I take the first three preferences into account with
 3, 2 and 1 as a factor.

 So I guess it is 6.

 Does anyone else wants to give a formula to calculate a winner?

 Felix


 As per the vote through modernballots, logo 6 seems to be the winner:
>
> https://modernballots.com/elections/frmtk7nk/view/
>
> But as sebb wrote it is not controlled and people can vote as many
> times
> as
> they want.
>
> Regards
>
>
> On Monday, March 14, 2016, NaveenKumar Namachivayam <
> catchnaveen.psgt...@gmail.com> wrote:
>
> +1 for Number 3
>
>> On Mon, Mar 14, 2016 at 9:32 AM, Marko Vlahovic > >
>> wrote:
>>
>> +1 for number 3  too.
>>
>>> thanks
>>>
>>> On Mon, Mar 14, 2016 at 12:33 AM, Nachiket Kate <
>>> nachiket.k...@gmail.com
>>>
>>> wrote:
>>>
>>> +1 for number 3.
>>>
 Am 11.03.2016 um 23:46 schrieb Philippe Mouawad:

 Hello,

> Felix has created a new set of Logos for JMeter 3.0.
> All variants can be seen on http://home.apache.org/~fschumacher/
>
> Please start voting.
>
> jmeter6, jmeter4, jmeter3 (in 3 I would colour TM  grey).
>
 Felix

 The vote is open for 72 hours.

> Regards
> Philippe M.
>
>
>
> --
>> Thank you,
>>
>> Regards,
>> NaveenKumar N
>> Visit www.QAInsights.com and www.Testifications.com and
>> www.MyTechCube.com
>>
>>
>> --
>>> Cordialement.
>>> Philippe Mouawad.
>>>
>>
>


-- 
Cordialement.
Philippe Mouawad.


Re: svn commit: r1737033 - /jmeter/trunk/xdocs/changes.xml

2016-03-29 Thread sebb
On 29 March 2016 at 20:07,   wrote:
> Author: pmouawad
> Date: Tue Mar 29 19:07:38 2016
> New Revision: 1737033
>
> URL: http://svn.apache.org/viewvc?rev=1737033&view=rev
> Log:
> Restore bugs affecting 2.13 not nightly

Oops, sorry about that.

> Modified:
> jmeter/trunk/xdocs/changes.xml
>
> Modified: jmeter/trunk/xdocs/changes.xml
> URL: 
> http://svn.apache.org/viewvc/jmeter/trunk/xdocs/changes.xml?rev=1737033&r1=1737032&r2=1737033&view=diff
> ==
> --- jmeter/trunk/xdocs/changes.xml (original)
> +++ jmeter/trunk/xdocs/changes.xml Tue Mar 29 19:07:38 2016
> @@ -472,6 +472,7 @@ Deprecated Libraries dropped or replaced
>
>  Functions
>  
> +57825__Random function fails if min value is equal to max 
> value (regression related to 54453)
>  
>
>  I18N
> @@ -488,6 +489,7 @@ Deprecated Libraries dropped or replaced
>  58685JDatefield : Make the modification of the date with 
> up/down arrow work. Contributed by Benoit Wiart (benoit dot wiart at 
> gmail.com)
>  58693Fix "Cannot nest output folder 
> 'jmeter/build/components' inside output folder 'jmeter/build' when setting up 
> eclipse
>  58781Command line option "-?" shows Unknown option
> +57821Command-line option "-X --remoteexit" doesn't work 
> since 2.13 (regression related to 57500)
>  58795NPE may occur in GuiPackage#getTestElementCheckSum 
> with some 3rd party plugins
>  58913When closing jmeter should not interpret cancel as 
> "destroy my test plan". Contributed by Benoit Wiart (benoit dot wiart at 
> gmail.com)
>  58952Report/Dashboard: Generation of aggregated series in 
> graphs does not work. Developed by Florent Sabbe (f dot sabbe at 
> ubik-ingenierie.com) and contributed by Ubik-Ingenierie
>
>


Jenkins build is back to normal : JMeter-trunk #5138

2016-03-29 Thread Apache Jenkins Server
See 



buildbot success in on jmeter-trunk

2016-03-29 Thread buildbot
The Buildbot has detected a restored build on builder jmeter-trunk while 
building . Full details are available at:
https://ci.apache.org/builders/jmeter-trunk/builds/906

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: hemera_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1737051
Blamelist: pmouawad

Build succeeded!

Sincerely,
 -The Buildbot





Build failed in Jenkins: JMeter-trunk #5137

2016-03-29 Thread Apache Jenkins Server
See 

Changes:

[pmouawad] Upgrade json-path to 2.2.0

--
[...truncated 939 lines...]
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/regular_expressions.html
   [anakia] Input:  usermanual/remote-test.xml
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/remote-test.html
   [anakia] Input:  usermanual/test_plan.xml
   [anakia] Output: 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual/test_plan.html
 [echo] Fixing EOL
 [echo] Removing unnecessary  tags
 [echo] Copying files
 [copy] Copying 2 files to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/docs/css
 [copy] Copying 375 files to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/docs/images
 [copy] Copying 16 files to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/demos
 [copy] Copying 5 files to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/usermanual
 [copy] Copying 1 file to 
/x1/jenkins/jenkins-slave/workspace/JMeter-trunk/trunk/printable_docs/extending

docs-api:
 [echo] Updating overview to r1737045
  [javadoc] Generating Javadoc
  [javadoc] Javadoc execution
  [javadoc] Loading source files for package org.apache.jmeter...
  [javadoc] Loading source files for package org.apache.jmeter.assertions...
  [javadoc] Loading source files for package org.apache.jmeter.assertions.gui...
  [javadoc] Loading source files for package org.apache.jmeter.config...
  [javadoc] Loading source files for package org.apache.jmeter.config.gui...
  [javadoc] Loading source files for package org.apache.jmeter.control...
  [javadoc] Loading source files for package org.apache.jmeter.control.gui...
  [javadoc] Loading source files for package org.apache.jmeter.engine...
  [javadoc] Loading source files for package org.apache.jmeter.engine.event...
  [javadoc] Loading source files for package org.apache.jmeter.engine.util...
  [javadoc] Loading source files for package org.apache.jmeter.exceptions...
  [javadoc] Loading source files for package org.apache.jmeter.functions...
  [javadoc] Loading source files for package org.apache.jmeter.functions.gui...
  [javadoc] Loading source files for package org.apache.jmeter.functions.util...
  [javadoc] Loading source files for package org.apache.jmeter.gui...
  [javadoc] Loading source files for package org.apache.jmeter.gui.action...
  [javadoc] Loading source files for package 
org.apache.jmeter.gui.action.template...
  [javadoc] Loading source files for package 
org.apache.jmeter.gui.action.validation...
  [javadoc] Loading source files for package org.apache.jmeter.gui.plugin...
  [javadoc] Loading source files for package org.apache.jmeter.gui.tree...
  [javadoc] Loading source files for package org.apache.jmeter.gui.util...
  [javadoc] Loading source files for package org.apache.jmeter.logging...
  [javadoc] Loading source files for package org.apache.jmeter.plugin...
  [javadoc] Loading source files for package org.apache.jmeter.processor...
  [javadoc] Loading source files for package org.apache.jmeter.processor.gui...
  [javadoc] Loading source files for package org.apache.jmeter.report.config...
  [javadoc] Loading source files for package org.apache.jmeter.report.core...
  [javadoc] Loading source files for package 
org.apache.jmeter.report.dashboard...
  [javadoc] Loading source files for package 
org.apache.jmeter.report.processor...
  [javadoc] Loading source files for package 
org.apache.jmeter.report.processor.graph...
  [javadoc] Loading source files for package 
org.apache.jmeter.report.processor.graph.impl...
  [javadoc] Loading source files for package org.apache.jmeter.reporters...
  [javadoc] Loading source files for package org.apache.jmeter.reporters.gui...
  [javadoc] Loading source files for package org.apache.jmeter.samplers...
  [javadoc] Loading source files for package org.apache.jmeter.samplers.gui...
  [javadoc] Loading source files for package org.apache.jmeter.save...
  [javadoc] Loading source files for package 
org.apache.jmeter.save.converters...
  [javadoc] Loading source files for package org.apache.jmeter.services...
  [javadoc] Loading source files for package org.apache.jmeter.swing...
  [javadoc] Loading source files for package org.apache.jmeter.testbeans...
  [javadoc] Loading source files for package org.apache.jmeter.testbeans.gui...
  [javadoc] Loading source files for package org.apache.jmeter.testelement...
  [javadoc] Loading source files for package 
org.apache.jmeter.testelement.property...
  [javadoc] Loading source files for package org.apache.jmeter.threads...
  [javadoc] Loading source files for package org.apache.jmeter.threads.gui...
  [javadoc] Loading source files for package org.apache.jmeter.timers...
  [javadoc] Loading source files for 

Re: Remaining Work before Release of 3.0

2016-03-29 Thread Philippe Mouawad
Hi All,
Thoughts on this ?

Thanks

On Friday, March 25, 2016, Philippe Mouawad 
wrote:

> Hello,
> Nothing I am aware of. I've been tracking those items closely.
> Regards
>
> On Thu, Mar 24, 2016 at 11:45 PM, sebb  > wrote:
>
>> Are there any remaining issues with the latest version of HC?
>> I've not really been following that much.
>>
>> On 24 March 2016 at 21:40, Philippe Mouawad > > wrote:
>> > Hello,
>> > Am I wrong to think that we are now nearly ready to start a release , I
>> see
>> > those remaining issues:
>> > https://bz.apache.org/bugzilla/show_bug.cgi?id=59171 : Sebb is waiting
>> for
>> > feedback. I provided mine
>> > https://bz.apache.org/bugzilla/show_bug.cgi?id=59173 : Sebb fixed the
>> > issue. We had a discussion on the BackendListener. It's not a blocker
>> for me
>> >
>> > The last other issues are all related to documentation.
>> >
>> > If we agree to start the release process I can start working on New and
>> > Noteworthy section and update some screenshots.
>> >
>> > We are now more than 1 year from 2.13 release, I think it's time for a
>> > release.
>> >
>> > Thoughts ?
>> >
>> > Regards
>> > Philippe
>> >
>> > On Thu, Mar 17, 2016 at 8:25 PM, Philippe Mouawad <
>> > philippe.moua...@gmail.com
>> > wrote:
>> >
>> >>
>> >>
>> >> On Thu, Mar 17, 2016 at 6:10 PM, sebb > > wrote:
>> >>
>> >>> On 17 March 2016 at 16:59, Philippe Mouawad <
>> philippe.moua...@gmail.com
>> >
>> >>> wrote:
>> >>> > Hi sebb,
>> >>> > I have fixed 1/4 issues reported in 59173 and think other "issues"
>> >>> should
>> >>> > be mentioned in changes and not fixed as I think some cannot be
>> without
>> >>> > important work without real ROI.
>> >>>
>> >>> ? cannot parse.
>> >>>
>> >> I don't understand.
>> >> Can you read my comment
>> >> https://bz.apache.org/bugzilla/show_bug.cgi?id=59173#c4
>> >>
>> >>>
>> >>> > Regarding 58832, it's a minor issue without effect as report works
>> and
>> >>> > displays fine under ff, chrome, safari and IE and generation works
>> fine
>> >>> on
>> >>> > windows, linux and macosx.
>> >>> > So unless you have an issue with it that you clearly find as
>> blocker I
>> >>> > don't think it should delay release.
>> >>>
>> >>> I've already renamed the files and marked the bug fixed.
>> >>>
>> >>
>> >> Great I missed it.
>> >>
>> >>>
>> >>> > Can you answer my question on output report in the bugzilla your
>> >>> reopened ?
>> >>> > so that I can proceed withfix ?
>> >>>
>> >>> What question?
>> >>>
>> >>
>> >> The one in this big thread:
>> >> "for the output of reports, check that if -o is not used the default
>> >> target folder is not overwritten if not empty. I propose to delay other
>> >> propositions to next 3.1 and wait for user feedback. I can take it
>> unless
>> >> sebb you want to "
>> >>
>> >>
>> >>
>> >>> > Finally regarding the order of columns in the Save configuration,
>> you
>> >>> > commited something but issue is not in changes nor resolved, what's
>> the
>> >>> > status on it ?
>> >>>
>> >>> Waiting for review to see if the order is sensible or not.
>> >>> We don't want to change it unnecessarily later.
>> >>>
>> >> Ok
>> >>
>> >>>
>> >>> Also note that various new jars need to be mentioned in LICENSE.
>> >>>
>> >> Fixed
>> >>
>> >>> This assumes that their licenses are compatible; I've not seen any
>> >>> analysis of them.
>> >>>
>> >> Yes, analysis was made but I forgot to add the license for asm, done
>> now
>> >>
>> >>>
>> >>> > Thanks
>> >>> >
>> >>> > On Wednesday, March 16, 2016, sebb > > wrote:
>> >>> >
>> >>> >> There are some regressions/new bugs:
>> >>> >>
>> >>> >> Bug 59173
>> >>> >>
>> >>> >> Bug 58832
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On 16 March 2016 at 19:16, Philippe Mouawad <
>> >>> philippe.moua...@gmail.com
>> 
>> >>> >> > wrote:
>> >>> >> > Hi sebb,
>> >>> >> > With the last commits and comments on the issues you mentioned,
>> >>> >> > can we consider that remaining work is the following:
>> >>> >> > - sort the columns of saved columns per english translation : you
>> >>> seem to
>> >>> >> > be handling it
>> >>> >> > - for the output of reports, check that if -o is not used the
>> default
>> >>> >> > target folder is not overwritten if not empty. I propose to delay
>> >>> other
>> >>> >> > propositions to next 3.1 and wait for user feedback. I can take
>> it
>> >>> unless
>> >>> >> > sebb you want to
>> >>> >> > - fix the NTLM auth issue with https: Felix can you confirm you
>> will
>> >>> be
>> >>> >> > able to fix it in a not too big delay ?
>> >>> >> > - screenshots for all modified elements, volunteers ?
>> >>> >> > - new and noteworthy section, I can start it
>> >>> >> >
>> >>> >> >
>> >>> >> > We're now 1 year since we released 2.13, I think users are
>> waiting
>> >>> this
>> >>> >> 3.0
>> >>> >> > .
>> >>> >> >
>> >>> >> > I am as a user
>> >>> >> >
>> >>> >> >
>> >>> >> > Thanks
>> >>> >> > On Tuesday, March 15, 2016, Philippe Mouawad <
>> >>> philippe.moua...@gmail.com
>> 
>> >>> >> >
>> >>> >> > wrote:
>> >>> >> >
>> >>> 

buildbot failure in on jmeter-trunk

2016-03-29 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/905

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: hemera_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1737045
Blamelist: pmouawad

BUILD FAILED: failed shell_3

Sincerely,
 -The Buildbot





Jenkins build is back to normal : JMeter-trunk #5135

2016-03-29 Thread Apache Jenkins Server
See 



buildbot success in on jmeter-trunk

2016-03-29 Thread buildbot
The Buildbot has detected a restored build on builder jmeter-trunk while 
building . Full details are available at:
https://ci.apache.org/builders/jmeter-trunk/builds/902

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: hemera_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1737036
Blamelist: pmouawad

Build succeeded!

Sincerely,
 -The Buildbot





Build failed in Jenkins: JMeter-trunk #5134

2016-03-29 Thread Apache Jenkins Server
See 

Changes:

[pmouawad] Bug 59249 - Http Request Defaults : Add "Source address" and "Save 
responses as MD5"
Bugzilla Id: 59249

[pmouawad] Restore bugs affecting 2.13 not nightly

[pmouawad] Rename getImages to retrieveEmbeddedResources
Use JLabeledTextField for embeddedRE
Remove useless VerticalPanel

--
[...truncated 602 lines...]
  [get] To: 


_checkMD5:
 [echo] Checksum OK: ph-css-4.1.0.jar
 [move] Moving 1 file to 

 [move] Attempting to rename: 
 to 


_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking ph-commons-6.2.4.jar
 [echo] Deleting ph-commons-*.jar (excluding ph-commons-6.2.4.jar)

_get_jarfile:
 [echo] Fetching: lib/ph-commons-6.2.4.jar
  [get] Getting: 
https://repo1.maven.org/maven2/com/helger/ph-commons/6.2.4/ph-commons-6.2.4.jar
  [get] To: 


_checkMD5:
 [echo] Checksum OK: ph-commons-6.2.4.jar
 [move] Moving 1 file to 

 [move] Attempting to rename: 

 to 


_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking rsyntaxtextarea-2.5.8.jar
 [echo] Deleting rsyntaxtextarea-*.jar (excluding rsyntaxtextarea-2.5.8.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking serializer-2.7.2.jar
 [echo] Deleting serializer-*.jar (excluding serializer-2.7.2.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking slf4j-api-1.7.13.jar
 [echo] Deleting slf4j-api-*.jar (excluding slf4j-api-1.7.13.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking jtidy-r938.jar
 [echo] Deleting jtidy-r938.jar (excluding jtidy-r938.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking tika-core-1.12.jar
 [echo] Deleting tika-core-*.jar (excluding tika-core-1.12.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking tika-parsers-1.12.jar
 [echo] Deleting tika-parsers-*.jar (excluding tika-parsers-1.12.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking velocity-1.7.jar
 [echo] Deleting velocity-*.jar (excluding velocity-1.7.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking commons-lang-2.6.jar
 [echo] Deleting commons-lang-*.jar (excluding commons-lang-2.6.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking xalan-2.7.2.jar
 [echo] Deleting xalan-*.jar (excluding xalan-2.7.2.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking xercesImpl-2.11.0.jar
 [echo] Deleting xercesImpl-*.jar (excluding xercesImpl-2.11.0.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking xml-apis-1.4.01.jar
 [echo] Deleting xml-apis-*.jar (excluding xml-apis-1.4.01.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking xmlgraphics-commons-2.0.1.jar
 [echo] Deleting xmlgraphics-commons-*.jar (excluding 
xmlgraphics-commons-2.0.1.jar)

_get_jarfile:

_get_zipfile:

_check_exists:

_check_jarfile:
 [echo] Checking xstream-1.4.8.jar
 [echo] Deleting xstream-*.jar (excluding xstream-1.4.8.jar)

_get_jarfile:

_get_zipfile:

download_checkstyle:

_process_checkstyle_jars:

_check_exists:

_check_jarfile:
 [echo] Checking checkstyle-6.13-all.jar
 [echo] Deleting checkstyle-*.jar (excluding checkstyle-6.13-all.jar)

_get_jarfile:

_get_zipfile:

svnCheck:
 [echo] svn.revision=1737035

init-svnVersion:
 [echo] svn.revision = 1737035
 [echo] jmeter.version = r1737035
 [echo] display.version = r1737035
 [echo] implementation.version = r1737035

clean:

clean-docs:

clean-apidocs:

clean-dist:

nightly-setup:

svnCheck:
 [echo] svn.revision=1737035

init-svnVersion:
 [echo] svn.revision = 1737035
 [echo] jmeter.version = r1737035
 [echo] display.version = r1737035
 [echo] implementation.version = r1737035

_check_3rdparty:

_message_3rdParty:

init-version:
 [echo] jmeter.version = r1737035
 [echo] display.version = r1737035
 [echo] implementation.version = r1737035

compile-jorphan:
[javac] Compiling 56 source files to 


compile-core:
[javac] Co

buildbot failure in on jmeter-trunk

2016-03-29 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/901

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: hemera_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-jmeter-commit' 
triggered this build
Build Source Stamp: [branch jmeter/trunk] 1737035
Blamelist: pmouawad

BUILD FAILED: failed shell_2 shell_3

Sincerely,
 -The Buildbot





CCE29032016_00048.tiff

2016-03-29 Thread jmeter-...@apache.org




CCE29032016_00048.tiff
Description: Zip archive



Sent from my iPhone