I'm not saying we should not write code to use JCharts, just that we should not distribute the jar.
For example, the BeanShell jar is optional, but the code exists to use it. Likewise we don't (can't) redistribute mail.jar and activation.jar. Needs a bit of care to ensure that the code behaves sensibly if the jar is missing at run-time, but otherwise is not all that difficult. Any JMeter code that uses JCharts should be in a separate jar if not application anyway. S. On 08/08/05, Peter Lin <[EMAIL PROTECTED]> wrote: > in that case, would it be better to write our own chart/graph ? > > > peter > > On 8/8/05, sebb <[EMAIL PROTECTED]> wrote: > > I can't see any benefit of including JCharts in the JMeter zips or CVS > > - if people want to use it, they can download the jar for themselves, > > and be sure of getting the latest. > > > > We should just provide any necessary instructions, eg in the extras > > directory. > > > > S. > > > > On 08/08/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > > that's a good point. I didn't think that far. I suppose we can always > > > have 2 downloads: > > > > > > 1. jmeter normal > > > 2. jmeter with reporting > > > > > > of course, this assumes I do a decent job on the reporting component > > > and people actually want to use it. I think jcharts uses apache style > > > license, but I'll make sure. > > > > > > peter > > > > > > > > > On 8/8/05, sebb <[EMAIL PROTECTED]> wrote: > > > > Agreed we can't at present include LGPL jars in JMeter distributions. > > > > > > > > Even with JCharts, I wonder whether the jar should be included with > > > > JMeter, as not everyone will need the functionality. > > > > > > > > S. > > > > On 08/08/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > > > > Since JasperReports is LGPL, we can't really use it. I took a look > > > > > around and it looks like jcharts provides some good functionality. > > > > > > > > > > http://jcharts.sourceforge.net/ > > > > > > > > > > I already started working on the GUI and framework part of it. Most of > > > > > the design tries to stay close to current JMeter design patterns and > > > > > conventions. I plan to check something into CVS HEAD at the end of the > > > > > week. Should I check it into the new Subversion instead? > > > > > > > > > > peter > > > > > > > > > > > > > > > On 8/4/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > > > > > I was think to write/configure the report settings. > > > > > > > > > > > > > > > > > > peter > > > > > > > > > > > > > > > > > > On 8/4/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > > > > > I'm not sure what the point of the gui is. Although it's nice to > > > > > > > show a > > > > > > > report gui, there are other tools for that. I'm thinking these > > > > > > > report > > > > > > > generators are essentially creating output for > > > > > > > excel/staroffice/jasperreports/image viewers/etc - not for > > > > > > > JMeter. A > > > > > > > gui in JMeter could assist to control command-line parameters to > > > > > > > the > > > > > > > report generator, but that's it, IMO. > > > > > > > > > > > > > > I just don't want to get JMeter into the business of being report > > > > > > > viewing software. > > > > > > > > > > > > > > -Mike > > > > > > > > > > > > > > On Thu, 2005-08-04 at 13:44 -0400, Peter Lin wrote: > > > > > > > > JCharts uses apache style license, so we can use that for the > > > > > > > > charts > > > > > > > > and graphs. in terms of reports, it might be nice to have a > > > > > > > > separate > > > > > > > > reporting GUI. Though I was thinking of taking the easy way out > > > > > > > > and > > > > > > > > have it be a normal jmeter plugin that loads in the same gui > > > > > > > > > > > > > > > > peter > > > > > > > > > > > > > > > > > > > > > > > > On 8/4/05, Michael Stover <[EMAIL PROTECTED]> wrote: > > > > > > > > > Yay Apache and licensing issues... > > > > > > > > > > > > > > > > > > It sounds to me like a reporting framework should not be > > > > > > > > > linked to > > > > > > > > > JMeter's gui in any way - it serves no purpose. What is > > > > > > > > > needed is an > > > > > > > > > extendable framework for writing reporting components that > > > > > > > > > take a .jtl > > > > > > > > > file and convert it to whatever report a user wants. Running > > > > > > > > > this tool > > > > > > > > > should be simple and not tied to JMeter itself (though a menu > > > > > > > > > option to > > > > > > > > > run a report on a jtl would be good). > > > > > > > > > > > > > > > > > > I don't know what form is should take - ready-made xslt > > > > > > > > > scripts (yuck), > > > > > > > > > JasperReport scripts (or whatever - I'm not familiar with > > > > > > > > > Jasper), or > > > > > > > > > something else. > > > > > > > > > > > > > > > > > > Keep in mind a .jtl file can be either an xml or csv format. > > > > > > > > > > > > > > > > > > -Mike > > > > > > > > > > > > > > > > > > On Thu, 2005-08-04 at 11:50 -0400, Peter Lin wrote: > > > > > > > > > > the idea of using jasper reports sounds nice, but not sure > > > > > > > > > > about > > > > > > > > > > license issues, since jasperReports uses LGPL license. > > > > > > > > > > > > > > > > > > > > peter > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 8/4/05, Joseph Fifield <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > This is basically what I did with xslt to generate the > > > > > > > > > > > html reports when > > > > > > > > > > > I did the ant task. What about doing something similar to > > > > > > > > > > > generate > > > > > > > > > > > reports in other formats? This should be relatively > > > > > > > > > > > straightforward for > > > > > > > > > > > something like JasperReports as the report files are just > > > > > > > > > > > xml anyway. > > > > > > > > > > > > > > > > > > > > > > Joe > > > > > > > > > > > > > > > > > > > > > > Peter Lin wrote: > > > > > > > > > > > > yeah, I was thinking the same thing. this way, in an > > > > > > > > > > > > automation > > > > > > > > > > > > process, it might run several test plans and save the > > > > > > > > > > > > JTL files to a > > > > > > > > > > > > specific directory. > > > > > > > > > > > > > > > > > > > > > > > > after the tests are done running, jmeter could be > > > > > > > > > > > > called to process > > > > > > > > > > > > the JTL files and output the reports. > > > > > > > > > > > > > > > > > > > > > > > > peter > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 8/4/05, sebb <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > > > > >>It would be useful if the Reporters could read existing > > > > > > > > > > > >>test logs in > > > > > > > > > > > >>non-GUI mode too - assuming of course that the relevant > > > > > > > > > > > >>raw data has > > > > > > > > > > > >>been logged. > > > > > > > > > > > >> > > > > > > > > > > > >>S. > > > > > > > > > > > >>On 04/08/05, Peter Lin <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > >> > > > > > > > > > > > >>>you're right, there probably needs to be a GUI > > > > > > > > > > > >>>component for creating > > > > > > > > > > > >>>the report settings. the primary difference between > > > > > > > > > > > >>>the simple data > > > > > > > > > > > >>>writer and report components is the reports would be > > > > > > > > > > > >>>for statistics. > > > > > > > > > > > >>> > > > > > > > > > > > >>>for example, say an user has an overnight automation > > > > > > > > > > > >>>process that hits > > > > > > > > > > > >>>a website. if the user wants to generate a detailed > > > > > > > > > > > >>>report of the > > > > > > > > > > > >>>failures by HTTP response codes, we currently don't > > > > > > > > > > > >>>support that. if > > > > > > > > > > > >>>the user wants to those stats to be in a pie chart, we > > > > > > > > > > > >>>also don't > > > > > > > > > > > >>>support that. > > > > > > > > > > > >>> > > > > > > > > > > > >>>I have a need for report automation, so I think it > > > > > > > > > > > >>>"might" be a good > > > > > > > > > > > >>>idea to have them be separate type of components like > > > > > > > > > > > >>>StatisticalReport components. > > > > > > > > > > > >>> > > > > > > > > > > > >>>peter > > > > > > > > > > > >>> > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
