Ben, allowed configuration of absolute output dir (see TraderScenario example).
Verified with trader example Ant build.xml. Can you please verify it works for you too (using latest svn version) before we push out bugfix release 2.5.2? Cheers On 24/04/2010 13:18, Mauro Talevi wrote: > Hi Ben, > > I've been able to reproduce issue in the JBehave examples > > https://jira.codehaus.org/browse/JBEHAVE-277 > > (had not been spotted because if the Ant scenarios run fine and if you don't > do an ant clean first, it will pick up the report outputs previously > outputted by IDE or Maven). > > We'll try to sort it out quickly. When do you need it by for your demo? > > Cheers > > On 24/04/2010 11:43, Ben Sullivan wrote: >> Hi folks >> >> I'm trying to get the reporting up and running for a small demo I'm >> putting together on BDD. >> >> I'm seeing some weird behaviour when executing the scenario runner >> through ant. >> >> When I run my scenario through a run configuration in IntelliJ I can >> see with the report files in the jbehave-reports directory which >> itself is contained in the directory I have configured IntelliJ to >> put compiled classes (<project_root>/out). All good. >> >> When I run through ant using InelliJ the report files appear in a >> bundled ant directory for IntelliJ: >> >> /Applications/IntelliJ%20IDEA%209.0.2.app/lib/ant/lib >> >> When I try and run with a raw ant installation from the command line >> I get the following: >> >> *~/work/bdd-demo $ ant run-scenarios* >> *Buildfile: build.xml* >> * >> * >> *setup:* >> * >> * >> *compile:* >> * >> * >> *compile-test:* >> * >> * >> *run-scenarios:* >> *[scenarioRunner] Running scenario >> au.com.nsqa.story.etl.SystemIntegration* >> *[scenarioRunner] Failure in runing scenarios: * >> *[scenarioRunner] au.com.nsqa.story.etl.SystemIntegration: >> java.io.FileNotFoundException: >> /usr/share/ant/lib/jbehave-reports/au.com.nsqa.story.etl.system_integration.stats >> (No such file or directory)* >> * >> * >> *BUILD SUCCESSFUL* >> *Total time: 0 seconds* >> * >> * >> It appears as though JBehave is trying to write to the root of the >> classpath directory for ant instead of the classpath root for my >> classes... >> >> I have attached my build file for reference, together with my >> scenario source. >> >> Any assistance would be much appreciated before I embark on a JBehave >> source debugging exercise! >> >> Thanks >> >> Ben >> >> >> >> >> >
