Re: Plugin market? (was: 3rd party jars - current and proposed)

Philippe>I know work on 3.0 is finished and milamber proposed to be rm right ? Sorry, I must have missed that. Philippe>But if you want we can discuss later after 3.0 Anytime works for me provided it does not delay 3.0. sebb>They don't care so much about memory footprint as they are not benchma

Re: Plugin market? (was: 3rd party jars - current and proposed)

I speak about unknown element. The plugins market needs no discussion, I'm 70% into implementing it. Andrey Pokhilko On 04/09/2016 11:05 PM, Philippe Mouawad wrote: > On Saturday, April 9, 2016, Andrey Pokhilko wrote: > >> Accepting bets on the discussion result... I'll better spend the time >>

Re: Plugin market? (was: 3rd party jars - current and proposed)

On 09/04/2016 21:12, Philippe Mouawad wrote: On Saturday, April 9, 2016, Vladimir Sitnikov wrote: Philippe>are you speaking about the plugin market or unknown element ? I like the idea of sebb: release 3.0, then discuss other subjects of matter. Does that work? yes but as far as I know w

Re: Plugin market? (was: 3rd party jars - current and proposed)

On Saturday, April 9, 2016, Vladimir Sitnikov wrote: > Philippe>are you speaking about the plugin market or unknown element ? > > I like the idea of sebb: release 3.0, then discuss other subjects of > matter. > > Does that work? yes but as far as I know work on 3.0 is finished and milamber prop

Re: Plugin market? (was: 3rd party jars - current and proposed)

Philippe>are you speaking about the plugin market or unknown element ? I like the idea of sebb: release 3.0, then discuss other subjects of matter. Does that work? Vladimir

Re: Plugin market? (was: 3rd party jars - current and proposed)

On Saturday, April 9, 2016, Andrey Pokhilko wrote: > Accepting bets on the discussion result... I'll better spend the time > writing code for "plugins market" than to have long discussions. Sorry, > that's my personal issues. > > For me you got the feature idea right, message transferred, so what

Re: Plugin market? (was: 3rd party jars - current and proposed)

Accepting bets on the discussion result... I'll better spend the time writing code for "plugins market" than to have long discussions. Sorry, that's my personal issues. For me you got the feature idea right, message transferred, so what to discuss :)? Andrey Pokhilko On 04/09/2016 10:21 PM, Phil

Re: Plugin market? (was: 3rd party jars - current and proposed)

what's the problem, let's discuss this in core On Saturday, April 9, 2016, Andrey Pokhilko wrote: > So you got the idea right. Unfortunately, this can't be done as > third-party plugin, it requires core change. > > Andrey Pokhilko > > On 04/09/2016 10:02 PM, Philippe Mouawad wrote: > > On Saturd

Re: Plugin market? (was: 3rd party jars - current and proposed)

So you got the idea right. Unfortunately, this can't be done as third-party plugin, it requires core change. Andrey Pokhilko On 04/09/2016 10:02 PM, Philippe Mouawad wrote: > On Saturday, April 9, 2016, Andrey Pokhilko wrote: > >> In fact, I'm already working on "plugins repository" feature. So

Re: Plugin market? (was: 3rd party jars - current and proposed)

On Saturday, April 9, 2016, Andrey Pokhilko wrote: > In fact, I'm already working on "plugins repository" feature. So it will > be available soon. > > What could be improved in JMeter regarding situation of unknown plugin > in test plan is to still show the test plan, putting some "Unknown Class

Re: 3rd party jars - current and proposed

@andrei, closing the pr is too early, afaiu only sebb is against it, the other either want to delay it or improve it. Thanks for the idea even if. we take it a bit further. On Friday, April 8, 2016, Andrey Pokhilko wrote: > Okay, thanks for reviewing. I will close the PR. > > Andrey Pokhilko >

Re: 3rd party jars - current and proposed

I answered in the new thread, great idea ! On Friday, April 8, 2016, Vladimir Sitnikov wrote: > Philippe> The idea was interesting because it makes things rather simple. > > What if we take a step back and consider some kind of "JMeter Plugin > Market"? > > For instance: > 1) Search & install pl

Re: Plugin market? (was: 3rd party jars - current and proposed)

On Saturday, April 9, 2016, sebb wrote: > On 9 April 2016 at 19:11, Philippe Mouawad > wrote: > > On Saturday, April 9, 2016, sebb > > wrote: > > > >> On 8 April 2016 at 22:40, Vladimir Sitnikov < > sitnikov.vladi...@gmail.com > >> > wrote: > >> > Philippe> The idea was interesting because it m

Re: Plugin market? (was: 3rd party jars - current and proposed)

On 9 April 2016 at 19:11, Philippe Mouawad wrote: > On Saturday, April 9, 2016, sebb wrote: > >> On 8 April 2016 at 22:40, Vladimir Sitnikov > > wrote: >> > Philippe> The idea was interesting because it makes things rather simple. >> > >> > What if we take a step back and consider some kind of "J

Re: Plugin market? (was: 3rd party jars - current and proposed)

On Saturday, April 9, 2016, sebb wrote: > On 8 April 2016 at 22:40, Vladimir Sitnikov > wrote: > > Philippe> The idea was interesting because it makes things rather simple. > > > > What if we take a step back and consider some kind of "JMeter Plugin > Market"? > > This is tangential to the subje

Listing directory content with the FTPSampler

Hello, I needed the ability to send the LIST FTP command from the FTPSampler for a test scenario at work. So I forked the project on GitHub and gave it a go. The result can be seen here: https://github.com/proudier/jmeter/commit/ff103720ee0d5f9b43dc54f56eb5778757bed936 Key aspects: - As the origi

Re: Plugin market? (was: 3rd party jars - current and proposed)

In fact, I'm already working on "plugins repository" feature. So it will be available soon. What could be improved in JMeter regarding situation of unknown plugin in test plan is to still show the test plan, putting some "Unknown Class Element" at the place of unknown classes. That would allow rev

Build failed in Jenkins: JMeter-trunk #5171

See Changes: [fschumacher] Write JMeter instead of jmeter [fschumacher] Correct typo -- [...truncated 1881 lines...] Loop5 C1=2 C2=1 C3=6,200,OK,Thread Group 1-1,text,true,,0,1,1,null,,1,0 If Test

[GitHub] jmeter pull request: Bug59294_BetterPercentileLabelv3

Github user milamberspace commented on a diff in the pull request: https://github.com/apache/jmeter/pull/187#discussion_r59113426 --- Diff: src/core/org/apache/jmeter/resources/messages_fr.properties --- @@ -853,7 +853,7 @@ reportgenerator_summary_statistics_kbytes=Ko/sec repor

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

See

[GitHub] jmeter pull request: Bug59291_FixDuplicateLineIngenerating-dashboa...

Github user asfgit closed the pull request at: https://github.com/apache/jmeter/pull/188 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

Re: 3rd party jars - current and proposed

On 8 April 2016 at 20:33, Philippe Mouawad wrote: > On Friday, April 8, 2016, sebb wrote: > >> There are currently 3 properties which can be used to augment the >> standard library directories >> (lib, lib/ext, lib/junit) >> >> A) search_paths >> B) user.classpath >> C) plugin_dependency_paths >>

Plugin market? (was: 3rd party jars - current and proposed)

On 8 April 2016 at 22:40, Vladimir Sitnikov wrote: > Philippe> The idea was interesting because it makes things rather simple. > > What if we take a step back and consider some kind of "JMeter Plugin Market"? This is tangential to the subject at hand. > For instance: > 1) Search & install plugin

[GitHub] jmeter pull request: Bug59294_BetterPercentileLabelv3

Github user ra0077 commented on the pull request: https://github.com/apache/jmeter/pull/187#issuecomment-207734589 Hi Vladimir, Thanks to your tips and advices I have juste make a rebase to have "clean properties files" and I have modify again the 2 files

[GitHub] jmeter pull request: Bug59294_BetterPercentileLabelv3

Github user ra0077 commented on a diff in the pull request: https://github.com/apache/jmeter/pull/187#discussion_r59111828 --- Diff: src/core/org/apache/jmeter/resources/messages_fr.properties --- @@ -853,7 +853,7 @@ reportgenerator_summary_statistics_kbytes=Ko/sec reportgenera

[GitHub] jmeter pull request: Bug59294_BetterPercentileLabelv3

Github user vlsi commented on the pull request: https://github.com/apache/jmeter/pull/187#issuecomment-207733923 @ra0077, thanks for the PRs, however could you please try reusing the PRs next time? Regarding "the right properties files", can you please clarify if you have to

[GitHub] jmeter pull request: Bug59294_BetterPercentileLabelv3

Github user milamberspace commented on a diff in the pull request: https://github.com/apache/jmeter/pull/187#discussion_r59111727 --- Diff: src/core/org/apache/jmeter/resources/messages_fr.properties --- @@ -853,7 +853,7 @@ reportgenerator_summary_statistics_kbytes=Ko/sec repor

[GitHub] jmeter pull request: Bug 59291 - Fix typo in generating-dashboard....

Github user ra0077 closed the pull request at: https://github.com/apache/jmeter/pull/183 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] jmeter pull request: Bug59291_FixDuplicateLineIngenerating-dashboa...

GitHub user ra0077 opened a pull request: https://github.com/apache/jmeter/pull/188 Bug59291_FixDuplicateLineIngenerating-dashboardDocumentation Hi, There is a typo in generating-dashboard.html I have remove the duplicate line (# Indicates which graph series are