On 19 May 2015 at 10:47, Vladimir Sitnikov <[email protected]> wrote: >>We cannot favour one 3rd party plugin over another > > We can/should favour all. > > JMeter's front page screams at you with "Highly Extensible core", > while it does not justify the claims. > It would be much better to put references to the relevant sections of > documentations and/or wiki. > > "Highly extensible" claim with zero useful extensions is of no use. > We all know there are good extensions, why don't we list some, so > users could easier get feel of the possibilities? > > Current JMeter wiki does reference lots of external sources: > http://wiki.apache.org/jmeter/ > > Here's what I got right from that http://wiki.apache.org/jmeter: > http://wiki.apache.org/jmeter/JMeterMavenPlugin > http://wiki.apache.org/jmeter/MysqlCollectorPlugin > http://wiki.apache.org/jmeter/MonitoringServers > http://wiki.apache.org/jmeter/LogAnalysis > etc. > > In other words, current JMeter's documentation favours some of the > plugins over another.
These pages are created by 3rd parties, not the JMeter project itself. Anyone who develops a plugin can create a Wiki account and request editting privileges in order to add links to their favourite plugins. That is very different from promoting specific plugin providers in the JMeter documentation. > >>We don't test and cannot recommend particular 3rd party plugins. > > At least Philippe, Andrey, and myself use "jmeter plugins" on a regular basis. > I have no idea if JMeter release procedure includes integration > testing with jmeter-plugins, but I believe JMeter should at lest > verify that "new JMeter version does not break plugins". > Obviously, JMeter cannot test against all the possible plugins, but it > is a good idea to test for compatibility with well-known plugins. No, I think that is out of scope for the JMeter project. It is up to the plugin authors to maintain and test their plugins and to provide user support for them. > I think j-p provides much higher level of quality than "mentioned in > JMeter's documentation > http://wiki.apache.org/jmeter/MysqlCollectorPlugin";, so the reference > to j-p in the JMeter's documentation is well deserved. That is on the Wiki, not in the JMeter core docs. > Here's what PostgreSQL does in similar case: > 1) The list of "external projects" right in the PostgreSQL core > documentation: > http://www.postgresql.org/docs/9.4/interactive/external-projects.html > "PostgreSQL is a complex software project, and managing the project is > difficult. We have found that many enhancements to PostgreSQL can be > more efficiently developed separately from the core project." That is what the JMeter Wiki is for. > 2) The list with _lots_ of external plugins/articles right in the > official wiki: > https://wiki.postgresql.org/wiki/Converting_from_other_Databases_to_PostgreSQL > , https://wiki.postgresql.org/wiki/Performance_Optimization Again, that belongs on the Wiki. Feel free to re-organise the JMeter Wiki more like the Postgres pages if you think that would help. > Vladimir
