[
http://jira.codehaus.org/browse/MOJO-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139556#action_139556
]
Stefan Bley commented on MOJO-1030:
-----------------------------------
I tried to use the chronos plugin with goal chronos:jmeter.
It fails saying
[WARNING] Attempting to build MavenProject instance for Artifact (org.codehaus.m
ojo:chronos-maven-plugin:1.0-20080407.102424-2) of type: maven-plugin; construct
ing POM artifact instead.
[INFO] [chronos:jmeter]
[INFO] No bootstrapper class found
[INFO] Excuting test D:\Projekte\ZAS\workspace\ZAS\zas\src\test\jmeter\test1.jmx
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at org.codehaus.mojo.chronos.jmeter.DependencyUtil.copyFileToDir(Depende
ncyUtil.java:99)
at org.codehaus.mojo.chronos.jmeter.DependencyUtil.copyDependencies(Depe
ndencyUtil.java:73)
at org.codehaus.mojo.chronos.jmeter.JMeterMojo.executeJmeter(JMeterMojo.
java:125)
at org.codehaus.mojo.chronos.jmeter.JMeterTestMojo.execute(JMeterTestMoj
o.java:155)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
Goal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Wed Jun 25 15:39:23 CEST 2008
[INFO] Final Memory: 3M/7M
[INFO] ------------------------------------------------------------------------
> Chronos: A plugin for contiuous performancetesting
> --------------------------------------------------
>
> Key: MOJO-1030
> URL: http://jira.codehaus.org/browse/MOJO-1030
> Project: Mojo
> Issue Type: New Feature
> Components: _Plugin Submission
> Reporter: Kent Soelvsten
> Attachments: chronos.zip, chronos.zip, chronos.zip
>
>
> At my company, we have developed a Maven2 plugin which we use for "continuous
> performancetesting".
> We use it to integrate performancetesting in our nightly Maven builds.
> The tests are performed using JMeter (it is pluggable though, other tools
> could potentially be used). The tests can be either Junittests or HTTP
> requests.
> It is possible to validate whether performancetargets have been met and
> generate nice reports of the results. The content of the reports are highly
> configurable.
> A few reports are built in (responsetimes, histograms, throughput and garbage
> collections). Through a plugin mechanism it is possible to add additional
> graphs to the generated report (ideas could be CPU usage over time or the
> size of an application servers connectionpool).
> Example reports can be seen at
> http://www.sosi.dk/sosi/seal/jmeter-scalability-report.html
> http://www.sosi.dk/sosi/seal/jmeter-endurance-report.html
> http://www.sosi.dk/sosi/seal/jmeter-response-report.html
> It is also possible to generate historical reports, allowing the user to see
> how performance has changed over time, thus helping him to pinpoint when a
> problem has been introduced.
> The code is attached her with an MIT license.
> Generate the site documentation and have a look at the examples!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
