If the JMeter devs want to put it in core I have no issue with that, however the plugin is a maven project an I don’t think maven projects are wanted in JMeter core :)
The website is down at the moment, it’s in the process of being moved over to github.io. (I should probably update the README to note that) > On 4 Mar 2016, at 09:51, Antonio Gomes Rodrigues <ra0...@gmail.com> wrote: > > Hi Mark, > > I don't have problem with JMeter-Maven-Plugin (and your documentation > rocks) in particularity > > It's only my experience with third party plugin in general and project with > only one developer. > And this experience is not always good and it's why I don't like to advise > my customer to use these projects/plugins > > One question, why don't integrate officially your plugin to JMeter core? > > About your website, I have a timeout :-( > > Thanks to your feedback > > Antonio > > > > > > > > > > Cet e-mail a été envoyé depuis un ordinateur protégé par Avast. > www.avast.com > <https://www.avast.com/fr-fr/lp-esg-win-01a?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=OA-2109-C> > <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > 2016-03-04 9:29 GMT+01:00 Mark Collin <mark.col...@lazeryattack.com>: > >> >>>>> Lack of official feature (JMeter plugin, Maven plugin, etc.) >>>> >>>> >>>> non official maven plugin exists and works rather nicely. >>>> What do you mean by JMeter plugin ? >>>> >>> >>> In general I have very bad experience with: >>> third party plugin (not well integrate, not well tested, not up to date >>> with the latest release, etc.) >>> Plugin maintained by only one person (less motivation by the developer, >>> etc.) >> >> Bug fixes for the maven plugin are happily accepted. Also please add >> issues for things that are: >> Not well integrated >> Not well tested >> Not up to date >> So that we can fix them ( >> https://github.com/jmeter-maven-plugin/jmeter-maven-plugin/issues). >> >> In regards to it being up to date: >> The plugin didn’t support JMeter 2.12 Because there were transitive >> dependency issues with the 2.12 maven release. >> There were also transitive dependency issues with the JMeter 2.13 release >> that we tried to work around. Version 1.10.1 of the plugin does use JMeter >> 2.13. >> Is there something else we have missed which makes you say it’s not up to >> date (Feedback is the only way we can make it better)? >> >> We are planning a version 2.0.0 of the plugin to coincide with a 3.0 >> JMeter release. The 2.0.0-SNAPSHOT is available in the Sonatype snapshots >> repository if you want to try it out and provide some feedback so that we >> can make it better that would be really useful.
