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 Tom Cellucci <tc...@gmail.com> on 2008/07/15 17:50:34 UTC
JMeter Maven and JMeter TestNG contribution
Hello,
I was recently working on a project where we wanted to run JMeter from our
Maven build process. At that time we installed the existing JMeterMojo,
tried it, and ended up making a few changes. My client has graciously
offered to contribute these changes back to the JMeter project, if you have
interest. Specifically these changes are:
(1) enhanced JMeterMojo that sets up a context class loader based on the
Maven project's test classpath (allows JMeter test classes to exist within
the maven project under test)
(2) a JMeter-TestNG integration that allows TestNG tests to run as part of a
JMeter test (supports ThreadGroup iterations, manages TestNG lifecycle
callbacks, etc)
Please let me know whether you would be interested in contribution of these
changes, and if so, how to proceed. Thank you,
-Tom
Re: JMeter Maven and JMeter TestNG contribution
Posted by Norval Hope <nr...@gmail.com>.
I'm also not a JMeter committer but would second the notion that maven
is a PITA, as I've had many runs ins with it in relation to ApacheDS.
It seems to take months to setup up all the publishing side of it, and
I absolutely cannot accept that you need to do a lot of extra
configuration if you want to guarantee the thing you built yesterday
will build the same today (at least I've been told it's possible to
configure it to allow a stable build). To me that is by far the most
crucial aspect of a build system, and auto-downloading of jars etc is
merely a nice to have.
I started out with an open mind about Maven, but now I think it is at
best mis-configured OOTB and at worst a bit misguided.
Also note that changing the source repository has a very bad effect on
people that are maintaining custom patches, like me, as they can no
longer do "svn diffs".
Norval
On Fri, Sep 19, 2008 at 2:58 AM, Peter Lin <wo...@gmail.com> wrote:
> I should state I am bias against maven. I believe getting jmeter to
> work with maven is feasible, but the cost of maintaining is going to
> be high. Although you can override the default directory structure,
> maven works best if you follow their "conventions".
>
> Since I don't actively work on jmeter these days I won't vote against
> it, but maven doesn't live up to the hype. I find it works well for a
> new project with simple dependencies. JMeter is a bit complex from a
> build perspective, since we use some jars that are not included in the
> build. Also, we tend to build components in a specific order, which
> isn't maven's strong point.
>
> peter
>
>
> On Thu, Sep 18, 2008 at 12:53 PM, sebb <se...@gmail.com> wrote:
>> On 18/09/2008, Tomasz Pik <to...@gmail.com> wrote:
>>> On Sat, Jul 19, 2008 at 3:21 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
>>> > Sebastian
>>> >
>>> > If you ever decide to port JMeter to Maven I will be willing to give you
>>> > a helping hand with that. We could still use the existing scripts to
>>> > build the distribution packages and generate the web site. It would be
>>> > beneficial, though, at least in my opinion, to use Maven to manage
>>> > dependencies and compile JMeter.
>>>
>>>
>>> Would it be possible to change directory structure of JMeter source tree
>>> a little, so it will be more 'maven friendly'?
>>> One change needs to be done - in directories with source code
>>> (like src/components) there should be at least one more level:
>>> src/components/java.
>>> Then there'll be natural place for pom.xml files:
>>> src/components/pom.xml
>>> src/components/java/org/apache/....
>>> Ideally, it should be src/components/src/main/java
>>> (OR components/src/main/java, with getting rid of top level
>>> src directory but I do not know if such a change would
>>> be acceptable to JMeter developers).
>>> Is there a chance to make such a change?
>>
>> The existing directory structure is not set in stone - it was changed
>> a year or two ago to move the test files into a separate directory
>> tree.
>>
>> However I don't think we should start on changing JMeter directory
>> structure in SVN until we are sure that the end result will work for
>> Maven.
>>
>> My personal view is that Maven should not be so picky about directory
>> structures, but so long as JMeter can still be built and tested using
>> Ant then I don't see a problem with moving the various chunks of the
>> source code tree around.
>>
>> I just don't think it makes sense to start on that process and then
>> find that there is some other aspect of the JMeter build process that
>> is not supported by Maven. For example there are three output
>> directories for jars (bin, lib, lib/ext) and lots of different jars.
>>
>>>
>>> Regards,
>>> Tomek
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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
>>
>>
>
> ---------------------------------------------------------------------
> 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: JMeter Maven and JMeter TestNG contribution
Posted by Peter Lin <wo...@gmail.com>.
I should state I am bias against maven. I believe getting jmeter to
work with maven is feasible, but the cost of maintaining is going to
be high. Although you can override the default directory structure,
maven works best if you follow their "conventions".
Since I don't actively work on jmeter these days I won't vote against
it, but maven doesn't live up to the hype. I find it works well for a
new project with simple dependencies. JMeter is a bit complex from a
build perspective, since we use some jars that are not included in the
build. Also, we tend to build components in a specific order, which
isn't maven's strong point.
peter
On Thu, Sep 18, 2008 at 12:53 PM, sebb <se...@gmail.com> wrote:
> On 18/09/2008, Tomasz Pik <to...@gmail.com> wrote:
>> On Sat, Jul 19, 2008 at 3:21 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
>> > Sebastian
>> >
>> > If you ever decide to port JMeter to Maven I will be willing to give you
>> > a helping hand with that. We could still use the existing scripts to
>> > build the distribution packages and generate the web site. It would be
>> > beneficial, though, at least in my opinion, to use Maven to manage
>> > dependencies and compile JMeter.
>>
>>
>> Would it be possible to change directory structure of JMeter source tree
>> a little, so it will be more 'maven friendly'?
>> One change needs to be done - in directories with source code
>> (like src/components) there should be at least one more level:
>> src/components/java.
>> Then there'll be natural place for pom.xml files:
>> src/components/pom.xml
>> src/components/java/org/apache/....
>> Ideally, it should be src/components/src/main/java
>> (OR components/src/main/java, with getting rid of top level
>> src directory but I do not know if such a change would
>> be acceptable to JMeter developers).
>> Is there a chance to make such a change?
>
> The existing directory structure is not set in stone - it was changed
> a year or two ago to move the test files into a separate directory
> tree.
>
> However I don't think we should start on changing JMeter directory
> structure in SVN until we are sure that the end result will work for
> Maven.
>
> My personal view is that Maven should not be so picky about directory
> structures, but so long as JMeter can still be built and tested using
> Ant then I don't see a problem with moving the various chunks of the
> source code tree around.
>
> I just don't think it makes sense to start on that process and then
> find that there is some other aspect of the JMeter build process that
> is not supported by Maven. For example there are three output
> directories for jars (bin, lib, lib/ext) and lots of different jars.
>
>>
>> Regards,
>> Tomek
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: JMeter Maven and JMeter TestNG contribution
Posted by sebb <se...@gmail.com>.
On 18/09/2008, Tomasz Pik <to...@gmail.com> wrote:
> On Sat, Jul 19, 2008 at 3:21 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
> > Sebastian
> >
> > If you ever decide to port JMeter to Maven I will be willing to give you
> > a helping hand with that. We could still use the existing scripts to
> > build the distribution packages and generate the web site. It would be
> > beneficial, though, at least in my opinion, to use Maven to manage
> > dependencies and compile JMeter.
>
>
> Would it be possible to change directory structure of JMeter source tree
> a little, so it will be more 'maven friendly'?
> One change needs to be done - in directories with source code
> (like src/components) there should be at least one more level:
> src/components/java.
> Then there'll be natural place for pom.xml files:
> src/components/pom.xml
> src/components/java/org/apache/....
> Ideally, it should be src/components/src/main/java
> (OR components/src/main/java, with getting rid of top level
> src directory but I do not know if such a change would
> be acceptable to JMeter developers).
> Is there a chance to make such a change?
The existing directory structure is not set in stone - it was changed
a year or two ago to move the test files into a separate directory
tree.
However I don't think we should start on changing JMeter directory
structure in SVN until we are sure that the end result will work for
Maven.
My personal view is that Maven should not be so picky about directory
structures, but so long as JMeter can still be built and tested using
Ant then I don't see a problem with moving the various chunks of the
source code tree around.
I just don't think it makes sense to start on that process and then
find that there is some other aspect of the JMeter build process that
is not supported by Maven. For example there are three output
directories for jars (bin, lib, lib/ext) and lots of different jars.
>
> Regards,
> Tomek
>
>
> ---------------------------------------------------------------------
> 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: JMeter Maven and JMeter TestNG contribution
Posted by Tomasz Pik <to...@gmail.com>.
On Sat, Jul 19, 2008 at 3:21 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
> Sebastian
>
> If you ever decide to port JMeter to Maven I will be willing to give you
> a helping hand with that. We could still use the existing scripts to
> build the distribution packages and generate the web site. It would be
> beneficial, though, at least in my opinion, to use Maven to manage
> dependencies and compile JMeter.
Would it be possible to change directory structure of JMeter source tree
a little, so it will be more 'maven friendly'?
One change needs to be done - in directories with source code
(like src/components) there should be at least one more level:
src/components/java.
Then there'll be natural place for pom.xml files:
src/components/pom.xml
src/components/java/org/apache/....
Ideally, it should be src/components/src/main/java
(OR components/src/main/java, with getting rid of top level
src directory but I do not know if such a change would
be acceptable to JMeter developers).
Is there a chance to make such a change?
Regards,
Tomek
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: JMeter Maven and JMeter TestNG contribution
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Wed, 2008-07-16 at 04:28 +0100, sebb wrote:
> On 15/07/2008, Tom Cellucci <tc...@gmail.com> wrote:
> > Hello,
> >
> > I was recently working on a project where we wanted to run JMeter from our
> > Maven build process. At that time we installed the existing JMeterMojo,
> > tried it, and ended up making a few changes. My client has graciously
> > offered to contribute these changes back to the JMeter project, if you have
> > interest.
>
> Thanks!
>
> > Specifically these changes are:
> >
> > (1) enhanced JMeterMojo that sets up a context class loader based on the
> > Maven project's test classpath (allows JMeter test classes to exist within
> > the maven project under test)
>
> The JMeter project does not currently use Maven and has no Maven
> add-ons, so it would not be easy to maintain/test.
>
> Perhaps your changes could be contributed back to the original
> JMeterMojo authors?
Sebastian
If you ever decide to port JMeter to Maven I will be willing to give you
a helping hand with that. We could still use the existing scripts to
build the distribution packages and generate the web site. It would be
beneficial, though, at least in my opinion, to use Maven to manage
dependencies and compile JMeter.
Oleg
>
> > (2) a JMeter-TestNG integration that allows TestNG tests to run as part of a
> > JMeter test (supports ThreadGroup iterations, manages TestNG lifecycle
> > callbacks, etc)
>
> This does sound like a useful addition to JMeter - there is already a
> JUnit sampler.
>
> > Please let me know whether you would be interested in contribution of these
> > changes, and if so, how to proceed. Thank you,
>
> Yes, we would be interested in the JMeter-TestNG addition.
>
> I assume this is a reasonably substantial piece of code, so it would
> be useful if the contributor(s) could provide CLAs:
>
> http://www.apache.org/licenses/#clas
>
> The code itself can be provided as an attachment to a Bugzilla issue.
> Please ensure that the appropriate Apache License headers are present
> in all source files.
>
> Thanks!
> >
> >
> > -Tom
> >
>
> ---------------------------------------------------------------------
> 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: JMeter Maven and JMeter TestNG contribution
Posted by sebb <se...@gmail.com>.
On 16/07/2008, Tom Cellucci <tc...@gmail.com> wrote:
> I have forwarded the request for the CLAs to my client, so hopefully the
> TestNG code can be contributed soon.
>
Thanks!
> As for the Maven plug-in, it was obtained from the JMeter wiki at
> http://wiki.apache.org/jakarta-jmeter/JMeterMavenPlugin . On that page
> there is a source tarball as well as a pre-built maven plug-in, but nothing
> in the way of project info. It appears that the page author's wiki login is
> 'timmccune'; I will try to reach him via e-mail. Would you know of any way
> to contact him? Thanks for any help.
>
Seems to be part of this:
http://mojo.codehaus.org/chronos-maven-plugin/
> -Tom
>
>
> ---------- Forwarded message ----------
> From: sebb <se...@gmail.com>
> Date: Tue, Jul 15, 2008 at 11:28 PM
> Subject: Re: JMeter Maven and JMeter TestNG contribution
> To: JMeter Developers List <jm...@jakarta.apache.org>
>
>
> On 15/07/2008, Tom Cellucci <tc...@gmail.com> wrote:
> > Hello,
> >
> > I was recently working on a project where we wanted to run JMeter from
> our
> > Maven build process. At that time we installed the existing JMeterMojo,
> > tried it, and ended up making a few changes. My client has graciously
> > offered to contribute these changes back to the JMeter project, if you
> have
> > interest.
>
> Thanks!
>
> > Specifically these changes are:
> >
> > (1) enhanced JMeterMojo that sets up a context class loader based on the
> > Maven project's test classpath (allows JMeter test classes to exist
> within
> > the maven project under test)
>
> The JMeter project does not currently use Maven and has no Maven
> add-ons, so it would not be easy to maintain/test.
>
> Perhaps your changes could be contributed back to the original
> JMeterMojo authors?
>
> > (2) a JMeter-TestNG integration that allows TestNG tests to run as part
> of a
> > JMeter test (supports ThreadGroup iterations, manages TestNG lifecycle
> > callbacks, etc)
>
> This does sound like a useful addition to JMeter - there is already a
> JUnit sampler.
>
> > Please let me know whether you would be interested in contribution of
> these
> > changes, and if so, how to proceed. Thank you,
>
> Yes, we would be interested in the JMeter-TestNG addition.
>
> I assume this is a reasonably substantial piece of code, so it would
> be useful if the contributor(s) could provide CLAs:
>
> http://www.apache.org/licenses/#clas
>
> The code itself can be provided as an attachment to a Bugzilla issue.
> Please ensure that the appropriate Apache License headers are present
> in all source files.
>
> Thanks!
> >
> >
> > -Tom
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
>
>
>
>
>
> --
> Thomas A. Cellucci
> Skill Corporation
> 440.360.0165
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Fwd: JMeter Maven and JMeter TestNG contribution
Posted by Tom Cellucci <tc...@gmail.com>.
I have forwarded the request for the CLAs to my client, so hopefully the
TestNG code can be contributed soon.
As for the Maven plug-in, it was obtained from the JMeter wiki at
http://wiki.apache.org/jakarta-jmeter/JMeterMavenPlugin . On that page
there is a source tarball as well as a pre-built maven plug-in, but nothing
in the way of project info. It appears that the page author's wiki login is
'timmccune'; I will try to reach him via e-mail. Would you know of any way
to contact him? Thanks for any help.
-Tom
---------- Forwarded message ----------
From: sebb <se...@gmail.com>
Date: Tue, Jul 15, 2008 at 11:28 PM
Subject: Re: JMeter Maven and JMeter TestNG contribution
To: JMeter Developers List <jm...@jakarta.apache.org>
On 15/07/2008, Tom Cellucci <tc...@gmail.com> wrote:
> Hello,
>
> I was recently working on a project where we wanted to run JMeter from
our
> Maven build process. At that time we installed the existing JMeterMojo,
> tried it, and ended up making a few changes. My client has graciously
> offered to contribute these changes back to the JMeter project, if you
have
> interest.
Thanks!
> Specifically these changes are:
>
> (1) enhanced JMeterMojo that sets up a context class loader based on the
> Maven project's test classpath (allows JMeter test classes to exist
within
> the maven project under test)
The JMeter project does not currently use Maven and has no Maven
add-ons, so it would not be easy to maintain/test.
Perhaps your changes could be contributed back to the original
JMeterMojo authors?
> (2) a JMeter-TestNG integration that allows TestNG tests to run as part
of a
> JMeter test (supports ThreadGroup iterations, manages TestNG lifecycle
> callbacks, etc)
This does sound like a useful addition to JMeter - there is already a
JUnit sampler.
> Please let me know whether you would be interested in contribution of
these
> changes, and if so, how to proceed. Thank you,
Yes, we would be interested in the JMeter-TestNG addition.
I assume this is a reasonably substantial piece of code, so it would
be useful if the contributor(s) could provide CLAs:
http://www.apache.org/licenses/#clas
The code itself can be provided as an attachment to a Bugzilla issue.
Please ensure that the appropriate Apache License headers are present
in all source files.
Thanks!
>
>
> -Tom
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
--
Thomas A. Cellucci
Skill Corporation
440.360.0165
Re: JMeter Maven and JMeter TestNG contribution
Posted by sebb <se...@gmail.com>.
On 15/07/2008, Tom Cellucci <tc...@gmail.com> wrote:
> Hello,
>
> I was recently working on a project where we wanted to run JMeter from our
> Maven build process. At that time we installed the existing JMeterMojo,
> tried it, and ended up making a few changes. My client has graciously
> offered to contribute these changes back to the JMeter project, if you have
> interest.
Thanks!
> Specifically these changes are:
>
> (1) enhanced JMeterMojo that sets up a context class loader based on the
> Maven project's test classpath (allows JMeter test classes to exist within
> the maven project under test)
The JMeter project does not currently use Maven and has no Maven
add-ons, so it would not be easy to maintain/test.
Perhaps your changes could be contributed back to the original
JMeterMojo authors?
> (2) a JMeter-TestNG integration that allows TestNG tests to run as part of a
> JMeter test (supports ThreadGroup iterations, manages TestNG lifecycle
> callbacks, etc)
This does sound like a useful addition to JMeter - there is already a
JUnit sampler.
> Please let me know whether you would be interested in contribution of these
> changes, and if so, how to proceed. Thank you,
Yes, we would be interested in the JMeter-TestNG addition.
I assume this is a reasonably substantial piece of code, so it would
be useful if the contributor(s) could provide CLAs:
http://www.apache.org/licenses/#clas
The code itself can be provided as an attachment to a Bugzilla issue.
Please ensure that the appropriate Apache License headers are present
in all source files.
Thanks!
>
>
> -Tom
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: JMeter Maven and JMeter TestNG contribution
Posted by Sascha Hofer <sa...@systema.info>.
Tom Cellucci wrote:
>
> Hello,
>
> I was recently working on a project where we wanted to run JMeter from our
> Maven build process. At that time we installed the existing JMeterMojo,
> tried it, and ended up making a few changes. My client has graciously
> offered to contribute these changes back to the JMeter project, if you
> have
> interest. Specifically these changes are:
>
> (1) enhanced JMeterMojo that sets up a context class loader based on the
> Maven project's test classpath (allows JMeter test classes to exist within
> the maven project under test)
> (2) a JMeter-TestNG integration that allows TestNG tests to run as part of
> a
> JMeter test (supports ThreadGroup iterations, manages TestNG lifecycle
> callbacks, etc)
>
> Please let me know whether you would be interested in contribution of
> these
> changes, and if so, how to proceed. Thank you,
>
> -Tom
>
>
What's the current state of these changes - I'm very interested in the
JMeter-TestNG integration and your enhancement of the JMeterMojo?
--
View this message in context: http://www.nabble.com/JMeter-Maven-and-JMeter-TestNG-contribution-tp18468606p19758354.html
Sent from the JMeter - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: JMeter Maven and JMeter TestNG contribution
Posted by sebb <se...@gmail.com>.
On 01/10/2008, Sascha Hofer <sa...@systema.info> wrote:
>
>
>
> Tom Cellucci wrote:
> >
> > Hello,
> >
> > I was recently working on a project where we wanted to run JMeter from our
> > Maven build process. At that time we installed the existing JMeterMojo,
> > tried it, and ended up making a few changes. My client has graciously
> > offered to contribute these changes back to the JMeter project, if you
> > have
> > interest. Specifically these changes are:
> >
> > (1) enhanced JMeterMojo that sets up a context class loader based on the
> > Maven project's test classpath (allows JMeter test classes to exist within
> > the maven project under test)
> > (2) a JMeter-TestNG integration that allows TestNG tests to run as part of
> > a
> > JMeter test (supports ThreadGroup iterations, manages TestNG lifecycle
> > callbacks, etc)
> >
> > Please let me know whether you would be interested in contribution of
> > these
> > changes, and if so, how to proceed. Thank you,
> >
> > -Tom
> >
> >
>
>
> What's the current state of these changes - I'm very interested in the
> JMeter-TestNG integration and your enhancement of the JMeterMojo?
I'm not aware of any Bugzilla enhancements relating to TestNG integration.
Perhaps you could try contacting the orginal poster.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org
Re: JMeter Maven and JMeter TestNG contribution
Posted by Sascha Hofer <sa...@systema.info>.
Tom Cellucci wrote:
>
> Hello,
>
> I was recently working on a project where we wanted to run JMeter from our
> Maven build process. At that time we installed the existing JMeterMojo,
> tried it, and ended up making a few changes. My client has graciously
> offered to contribute these changes back to the JMeter project, if you
> have
> interest. Specifically these changes are:
>
> (1) enhanced JMeterMojo that sets up a context class loader based on the
> Maven project's test classpath (allows JMeter test classes to exist within
> the maven project under test)
> (2) a JMeter-TestNG integration that allows TestNG tests to run as part of
> a
> JMeter test (supports ThreadGroup iterations, manages TestNG lifecycle
> callbacks, etc)
>
> Please let me know whether you would be interested in contribution of
> these
> changes, and if so, how to proceed. Thank you,
>
> -Tom
>
>
What's the current state of these changes - I'm very interested in the
JMeter-TestNG integration and your enhancement of the JMeterMojo?
--
View this message in context: http://www.nabble.com/JMeter-Maven-and-JMeter-TestNG-contribution-tp18468606p19758355.html
Sent from the JMeter - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-dev-help@jakarta.apache.org