I am wondering if there is developer support for the idea of converting
JMeter's build process to be based on Maven. If there is suitable support of
this idea, I was going to start writing a conversion script that would
convert the project sources while maintaining as much scm history as
possible.
On 25 November 2010 14:18, Peter Lynch wrote:
> I am wondering if there is developer support for the idea of converting
> JMeter's build process to be based on Maven. If there is suitable support of
> this idea, I was going to start writing a conversion script that would
> convert the project sour
Just a heads up that I'm currently working on trying to combine the
HTTP implementations (Java, HttpClient3) into a single GUI, with
run-time choice of implementation.
The rationale for this is that HttpClient 4 is now available, and it
would be good to add that, but I think we should keep HttpCli
Hi sebb,
On Thu, Nov 25, 2010 at 9:42 AM, sebb wrote:
> On 25 November 2010 14:18, Peter Lynch wrote:
> > I am wondering if there is developer support for the idea of converting
> > JMeter's build process to be based on Maven. If there is suitable support
> of
> > this idea, I was going to star
I've accepted the message below from the moderation queue, but please
subscribe using your .ca address if you intend to keep posting to this
list from it.
-Rahul
On Thu, Nov 25, 2010 at 12:54 PM, Peter Lynch wrote:
> Hi sebb,
>
> On Thu, Nov 25, 2010 at 9:42 AM, sebb wrote:
>
>> On 25 November
On 25 November 2010 17:54, Peter Lynch wrote:
> Hi sebb,
>
> On Thu, Nov 25, 2010 at 9:42 AM, sebb wrote:
>
>> On 25 November 2010 14:18, Peter Lynch wrote:
>> > I am wondering if there is developer support for the idea of converting
>> > JMeter's build process to be based on Maven. If there is
I hate maven and it sucks. It does not reduce maintenance at all. I vote
against changing to maven.
-1
Maven is a road to he'll on my book
Sent from my iPhone
On Nov 25, 2010, at 1:28 PM, sebb wrote:
> On 25 November 2010 17:54, Peter Lynch wrote:
>> Hi sebb,
>>
>> On Thu, Nov 25, 2010 a
In my experience the value would be for publishing to public
repositories, but having tried to go thru the process for sonatype, and
failing miserably, i'd second peter's opinion. Maven is just a nasty
thing to have to deal with.
As i'm just a lurker with regards to jmeter, tho, take my opinio
This community is a Meritocracy, not a Democracy. "What's the difference?",
you ask.
In a Democracy you have a vote, you can cast your vote for various reasons, no
one asks "why" if you vote a certain way. There's no abstract idea of "merit".
At Apache you certainly have a "vote" in a cons
even though I haven't been active in jmeter in a while, I am still a
jmeter committer.
quite honestly, I've seen maven work first hand.
1. the claim it reduces maintenance has not truth. My first hand
experience is that it creates a much bigger burden.
2. changing the directory structure of jmet
On Nov 25, 2010, at 2:29 PM, Peter Lin wrote:
> even though I haven't been active in jmeter in a while, I am still a
> jmeter committer.
>
Quantify "a while".
I'm still a committee on various projects. Would I veto a change by someone
with a defined need who shows initiative? No.
If Pete
On Thu, Nov 25, 2010 at 3:44 PM, Tim O'Brien wrote:
> On Nov 25, 2010, at 2:29 PM, Peter Lin wrote:
>
>> even though I haven't been active in jmeter in a while, I am still a
>> jmeter committer.
>>
>
> Quantify "a while".
>
No need, we have archives for the curious.
> I'm still a committee on
Hello,
Your plan seems very well.
Keep legacy samplers (Java, Hc3) is a good things, but perhaps if there
has three http samplers thus will introduce some confusing for a new
user? (what http sampler is the best for my test?)
(Actually, my understanding is the Java Http sampler is the legacy and
honestly, I don't remember the last time I committed changes for
jmeter. it was a bug fix in something I wrote 5-6 years back.
I've contributed quite a bit of stuff to jmeter in the past and still
use it. For me, jmeter is a mature stable product that meets all of my
needs, so I haven't needed any
On 25 November 2010 23:13, Milamber wrote:
> Hello,
>
> Your plan seems very well.
>
> Keep legacy samplers (Java, Hc3) is a good things, but perhaps if there
> has three http samplers thus will introduce some confusing for a new
> user? (what http sampler is the best for my test?)
It will have t
Truthfully the main motivation for proposing to use Maven to build JMeter is
to increase the chances of getting more people involved in the project, to
fix bugs, to send patches and add features.
Honestly do we expect the majority of potential developers to run for the
hills and the project to die
so far I am not convinced of the benefits of changing to maven.
my vote is still -1
As I said before, my feeling is jmeter is mature and stable. JMeter
isn't missing any critical features and seb has done a phenominal job
of maintaining it.
It's not like there's 10 critical features JMeter must
Peter Lin,
On Thu, Nov 25, 2010 at 10:49 PM, Peter Lin wrote:
> so far I am not convinced of the benefits of changing to maven.
>
> my vote is still -1
>
> As I said before, my feeling is jmeter is mature and stable. JMeter
> isn't missing any critical features and seb has done a phenominal job
On Fri, Nov 26, 2010 at 12:08 AM, Peter Lynch wrote:
> Peter Lin,
>
>
> On Thu, Nov 25, 2010 at 10:49 PM, Peter Lin wrote:
>
>> so far I am not convinced of the benefits of changing to maven.
>>
>> my vote is still -1
>>
>> As I said before, my feeling is jmeter is mature and stable. JMeter
>> is
19 matches
Mail list logo
