JMeter has just been offered a Maven plugin for creating reports.
Rather than include the code in JMeter, I think it would be better
hosted at mojo.codehaus.org, along with the other Maven plugins.
That got me thinking - perhaps a similar idea could be set up for
JMeter plugins?
Or is that a
Any particular reason, why this can not be a part of the JMeter project?
Splitting a rather small community into two parts (apache + codehaus)
does not sound too good. Having that plugin inside the JMeter project
might lead to new hands helping out with JMeter itself.
Gaining gravity in the
I don't see it as splitting the community, rather as an adjunct to the
existing community.
One of the reasons would be to allow independent release cycles.
Also, not every user would need all the plugins.
Perhaps this could be done by rearranging the JMeter project, but it
seems cleaner to have
Hm,
why shouldn't it be possible to do two independent products (JMeter +
Maven Plugin) on different release cycles in one project? Other projects
do this all the time (e.g. Turbine for a very long time with all the
Fulcrum stuff, META etc).
Still no need for a split for me.
Best
On 10/6/07, sebb [EMAIL PROTECTED] wrote:
JMeter has just been offered a Maven plugin for creating reports.
Rather than include the code in JMeter, I think it would be better
hosted at mojo.codehaus.org, along with the other Maven plugins.
Agreed.
That got me thinking - perhaps a similar
