Hi Tom,

I'm using the following command : mvn clean site.
"clean" reset the old performance results.
With this and the previous pom.xml, it's working fine.
I'm using a clean install of maven 2.0.9 and not the libs embedded in the
eclipse plugin.

Regards,

Bj

Tom Purcell wrote:
> 
> Bj
> 
> I'm getting the exact same stack trace (both from within Intellij and from
> the command line). Could you share what you enter on the command line?
> 
> Thanks
> Tom
>  
> 
> Benj wrote:
>> 
>> Ok it works fine with maven (2.0.9) used in command line.
>> I was using eclipse and the m2e plugin.
>> 
>> -- 
>> Bj
>> 
>> 
>> Benj wrote:
>>> 
>>> Hi,
>>> 
>>> I'm trying to use the maven chronos plugin with the historyreports goal
>>> but I didn't manage to make it works.
>>> The following goals work fine : jmeter,report,jmetergui. savehistory
>>> seems to work but I'm not really sure.
>>> 
>>> Here is the stacktrace :
>>> "Error message: Mojo: post-integration-test (referenced by:
>>> historyreport) does not exist in plugin:
>>> org.codehaus.mojo:chronos-maven-plugin:1.0-SNAPSHOT.
>>> Root error message: Mojo: post-integration-test (referenced by:
>>> historyreport) does not exist in plugin:
>>> org.codehaus.mojo:chronos-maven-plugin:1.0-SNAPSHOT.
>>> 
>>> Error stacktrace:
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> construct build plan for: test-chronos
>>> Id: test-chronos:test-chronos:jar:0.0.1-SNAPSHOT
>>> task-segment: [chronos:historyreport]. Reason: Mojo:
>>> post-integration-test (referenced by: historyreport) does not exist in
>>> plugin: org.codehaus.mojo:chronos-maven-plugin:1.0-SNAPSHOT.
>>>     at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:414)
>>>     at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmentForProject(DefaultLifecycleExecutor.java:235)
>>>     at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:191)
>>>     at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
>>>     at
>>> org.apache.maven.DefaultMaven.execute_aroundBody0(DefaultMaven.java:223)
>>>     at
>>> org.apache.maven.DefaultMaven.execute_aroundBody1$advice(DefaultMaven.java:304)
>>>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:1)
>>>     at
>>> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody2(MavenEmbedder.java:904)
>>>     at
>>> org.apache.maven.embedder.MavenEmbedder.execute_aroundBody3$advice(MavenEmbedder.java:304)
>>>     at
>>> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:1)
>>>     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:176)
>>>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:63)
>>>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:52)
>>> Caused by: org.apache.maven.lifecycle.plan.LifecyclePlannerException:
>>> Mojo: post-integration-test (referenced by: historyreport) does not
>>> exist in plugin: org.codehaus.mojo:chronos-maven-plugin:1.0-SNAPSHOT.
>>>     at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.recurseSingleMojoFork(DefaultBuildPlanner.java:501)
>>>     at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.findForkModifiers(DefaultBuildPlanner.java:380)
>>>     at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.findForkModifiers(DefaultBuildPlanner.java:211)
>>>     at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.addForkedLifecycleModifiers(DefaultBuildPlanner.java:179)
>>>     at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody0(DefaultBuildPlanner.java:117)
>>>     at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan_aroundBody1$advice(DefaultBuildPlanner.java:403)
>>>     at
>>> org.apache.maven.lifecycle.plan.DefaultBuildPlanner.constructBuildPlan(DefaultBuildPlanner.java:1)
>>>     at
>>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.getLifecycleBindings(DefaultLifecycleExecutor.java:400)
>>>     ... 12 more"
>>> 
>>> Can someone help me ? Is these feature (historyreport) really included
>>> in the 1.0.0-SNAPSHOT ?
>>> 
>>> Here's my pom.xml
>>> <project xmlns="http://maven.apache.org/POM/4.0.0";
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
>>> http://maven.apache.org/maven-v4_0_0.xsd";>
>>>   <modelVersion>4.0.0</modelVersion>
>>>   <groupId>test-chronos</groupId>
>>>   <artifactId>test-chronos</artifactId>
>>>   <name>test-chronos</name>
>>>   <version>0.0.1-SNAPSHOT</version>
>>>   <description/>
>>>     <properties>
>>>      <jmeter.home>/opt/jakarta-jmeter-2.3.1</jmeter.home>
>>>    </properties>
>>> 
>>> 
>>>   <build>
>>>   <pluginManagement>
>>>       <plugins>
>>>         <plugin>
>>>           <groupId>org.codehaus.mojo</groupId>
>>>           <artifactId>chronos-maven-plugin</artifactId>
>>>           <version>1.0-SNAPSHOT</version>
>>>         </plugin>
>>>       </plugins>
>>>     </pluginManagement>
>>>  
>>>       <plugins>
>>>           <plugin>
>>>             <groupId>org.codehaus.mojo</groupId>
>>>             <artifactId>chronos-maven-plugin</artifactId>
>>>             <version>1.0-SNAPSHOT</version>
>>>             <configuration>
>>>                
>>> <historydir>${basedir}/chronos/history/performancetest</historydir>
>>>                
>>> <input>${basedir}/src/main/resources/simplewebplan.jmx</input>
>>>             </configuration>
>>>             <executions>
>>>                 <execution>
>>>                     <id>simpletest</id>
>>>                     <goals>
>>>                         <goal>jmeter</goal>
>>>                         <goal>savehistory</goal>
>>>                     </goals>
>>>                 </execution>
>>>             </executions>
>>>           </plugin>
>>>       </plugins>
>>>      
>>>   </build>
>>> 
>>>   <repositories>
>>>       <repository>
>>>           <id>Codehaus snapshots</id>
>>>           <name>codehaus_snapshots</name>
>>>           <url>http://snapshots.repository.codehaus.org/</url>
>>>            <snapshots>
>>>         <enabled>true</enabled>
>>>       </snapshots>
>>>       <releases>
>>>         <enabled>false</enabled>
>>>       </releases>
>>>       </repository>
>>>   </repositories>
>>>   <pluginRepositories>
>>>       <pluginRepository>
>>>           <id>codehaus snapshots plugin</id>
>>>           <name>codehaus_snapshots_plugins</name>
>>>           <url>http://snapshots.repository.codehaus.org/</url>
>>>            <snapshots>
>>>         <enabled>true</enabled>
>>>       </snapshots>
>>>       <releases>
>>>         <enabled>false</enabled>
>>>       </releases>
>>>      </pluginRepository>
>>>   </pluginRepositories>
>>>   <dependencies>
>>>   </dependencies>
>>>   <distributionManagement>
>>>       <snapshotRepository>
>>>           <id>codehause_snap</id>
>>>           <name>codehaus_snap</name>
>>>           <url>http://snapshots.repository.codehaus.org/</url>
>>>       </snapshotRepository>
>>>   </distributionManagement>
>>> </project>
>>> 
>>> Best regards,
>>> 
>>> -- 
>>> Bj
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Maven-codehaus-chronos-plugin-issue-tp19305626p19573928.html
Sent from the mojo - user mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to