You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jmeter-dev@jakarta.apache.org by Peter Lin <wo...@gmail.com> on 2004/10/11 21:03:21 UTC
2_0 vs Head
I noticed the Distribution graph wasn't in 2_0 branch. When I compare
2_0 to head, I see a lot of differences like ObjectTableModel.
do we want to merge that back to 2_0. I think many of the changes
include the updates Mike made for XStream.
I think it's worth while to include those changes, since the updates
to aggregate listener and view results in table need those updates.
thoughts?
peter
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: 2_0 vs Head
Posted by Peter Lin <wo...@gmail.com>.
the docs are already in 2_0 branch.
the code hasn't been merged with 2_0 branch. Although I don't use the
LDAP sampler, I think it would be good to have it.
peter
On Tue, 12 Oct 2004 08:26:47 +0200, Dolf Smits <do...@zonnet.nl> wrote:
> Hi,
>
> I would like to have the extended ldap included.
> It's stable now and I'm wondering whether people will use it and find any
> more bugs (or want enhancements)
>
> Dolf
>
> ----- Original Message -----
> From: "Peter Lin" <wo...@gmail.com>
> To: "jmeter-dev" <jm...@jakarta.apache.org>
> Sent: Tuesday, October 12, 2004 01:18
> Subject: Re: 2_0 vs Head
> in table and aggregate listener. those depend on changes
>
> >
> > do we plan on making the extended ldap stuff part of 2.0.2 ?
> >
> > I'm fine either way, since I'm more focused on the new jms and ejb
> samplers.
> >
> > peter
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: 2_0 vs Head
Posted by Dolf Smits <do...@zonnet.nl>.
Hi,
I would like to have the extended ldap included.
It's stable now and I'm wondering whether people will use it and find any
more bugs (or want enhancements)
Dolf
----- Original Message -----
From: "Peter Lin" <wo...@gmail.com>
To: "jmeter-dev" <jm...@jakarta.apache.org>
Sent: Tuesday, October 12, 2004 01:18
Subject: Re: 2_0 vs Head
in table and aggregate listener. those depend on changes
>
> do we plan on making the extended ldap stuff part of 2.0.2 ?
>
> I'm fine either way, since I'm more focused on the new jms and ejb
samplers.
>
> peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: 2_0 vs Head
Posted by Peter Lin <wo...@gmail.com>.
On Mon, 11 Oct 2004 22:17:18 +0100, sebb <se...@gmail.com> wrote:
> On Mon, 11 Oct 2004 15:40:26 -0500, Peter Lin <wo...@gmail.com> wrote:
> > I think mike is done with the new JMX file format stuff. I would vote
> > for merging it to 2.0.2, since the AOP, JMS sampler and EJB sampler
> > are fairly major changes/additions.
>
> I'm really not keen on changing the JMX format before 2.0.2 is released.
>
> There have been a lot of bug fixes to 2.0, but so far no fundamental
> changes, as far as I can
> remember. There is some new functionality, but I don't think the
> underlying code has changed much.
I can understand that reasoning. In that case, I should revert the
distribution graph stuff, since it requires some of the changes in
jorphan in HEAD. Related to that, I should probably also revert the
changes to the documentation for distribution graph, extended LDAP,
view result in table and aggregate listener. those depend on changes
to ObjectTableModel and a couple of other changes in HEAD.
I don't know exactly where the changes end and begin in terms of new JMX format.
>
> We should release 2.0.2 as a bug fix release, and then consider what
> else to add in.
>
> I don't think AOP/Java 1.5 should be included in a 2.x release.
I agree with that.
>
> > By the end of the week I was hoping to start checking in some things
> > for the JMS sampler to HEAD, but I am holding off until it's safe.
>
> What's unsafe about that? Surely HEAD (at present) is where all the
> major new stuff is going?
>
safe was probably the wrong choice of words. what I meant was,
there's going to be lots of changes. if we wanted to make a 2.1.x
release, checking in the changes for jms and ejb would make it harder
to figure out what changes to core classes are needed.
I'm thinking I should have an experimental branch locally for myself
to avoid making it harder on releases. A quick summary of the merge I
did today for the docs.
aggregate listener
view results in table
view results tree
extended ldap
ldap
jdbc
do we plan on making the extended ldap stuff part of 2.0.2 ?
I'm fine either way, since I'm more focused on the new jms and ejb samplers.
peter
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: 2_0 vs Head
Posted by sebb <se...@gmail.com>.
On Mon, 11 Oct 2004 15:40:26 -0500, Peter Lin <wo...@gmail.com> wrote:
> I think mike is done with the new JMX file format stuff. I would vote
> for merging it to 2.0.2, since the AOP, JMS sampler and EJB sampler
> are fairly major changes/additions.
I'm really not keen on changing the JMX format before 2.0.2 is released.
There have been a lot of bug fixes to 2.0, but so far no fundamental
changes, as far as I can
remember. There is some new functionality, but I don't think the
underlying code has changed much.
We should release 2.0.2 as a bug fix release, and then consider what
else to add in.
I don't think AOP/Java 1.5 should be included in a 2.x release.
> By the end of the week I was hoping to start checking in some things
> for the JMS sampler to HEAD, but I am holding off until it's safe.
What's unsafe about that? Surely HEAD (at present) is where all the
major new stuff is going?
> Mike is actually around, so hopefully he'll explain the impact of the
> JMX format changes.
>
> peter
>
>
>
>
> On Mon, 11 Oct 2004 21:31:28 +0100, sebb <se...@gmail.com> wrote:
> >
> >
> > On Mon, 11 Oct 2004 14:03:21 -0500, Peter Lin <wo...@gmail.com> wrote:
> > > I noticed the Distribution graph wasn't in 2_0 branch. When I compare
> > > 2_0 to head, I see a lot of differences like ObjectTableModel.
> > >
> > > do we want to merge that back to 2_0. I think many of the changes
> > > include the updates Mike made for XStream.
> > >
> > > I think it's worth while to include those changes, since the updates
> > > to aggregate listener and view results in table need those updates.
> > >
> > > thoughts?
> > >
> >
> > If it means including the new JMX file format and some of the other
> > changes, I would say wait for a later release, e.g. 2.0.3. However, if
> > it can be included without impacting anything else, then it could go
> > in 2.0.2.
> >
> > I think it's important to get out a new release soon with all the
> > various bug fixes, and then have a stable base to build on.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: 2_0 vs Head
Posted by Peter Lin <wo...@gmail.com>.
I think mike is done with the new JMX file format stuff. I would vote
for merging it to 2.0.2, since the AOP, JMS sampler and EJB sampler
are fairly major changes/additions.
By the end of the week I was hoping to start checking in some things
for the JMS sampler to HEAD, but I am holding off until it's safe.
Mike is actually around, so hopefully he'll explain the impact of the
JMX format changes.
peter
On Mon, 11 Oct 2004 21:31:28 +0100, sebb <se...@gmail.com> wrote:
>
>
> On Mon, 11 Oct 2004 14:03:21 -0500, Peter Lin <wo...@gmail.com> wrote:
> > I noticed the Distribution graph wasn't in 2_0 branch. When I compare
> > 2_0 to head, I see a lot of differences like ObjectTableModel.
> >
> > do we want to merge that back to 2_0. I think many of the changes
> > include the updates Mike made for XStream.
> >
> > I think it's worth while to include those changes, since the updates
> > to aggregate listener and view results in table need those updates.
> >
> > thoughts?
> >
>
> If it means including the new JMX file format and some of the other
> changes, I would say wait for a later release, e.g. 2.0.3. However, if
> it can be included without impacting anything else, then it could go
> in 2.0.2.
>
> I think it's important to get out a new release soon with all the
> various bug fixes, and then have a stable base to build on.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: 2_0 vs Head
Posted by sebb <se...@gmail.com>.
On Mon, 11 Oct 2004 14:03:21 -0500, Peter Lin <wo...@gmail.com> wrote:
> I noticed the Distribution graph wasn't in 2_0 branch. When I compare
> 2_0 to head, I see a lot of differences like ObjectTableModel.
>
> do we want to merge that back to 2_0. I think many of the changes
> include the updates Mike made for XStream.
>
> I think it's worth while to include those changes, since the updates
> to aggregate listener and view results in table need those updates.
>
> thoughts?
>
If it means including the new JMX file format and some of the other
changes, I would say wait for a later release, e.g. 2.0.3. However, if
it can be included without impacting anything else, then it could go
in 2.0.2.
I think it's important to get out a new release soon with all the
various bug fixes, and then have a stable base to build on.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org