[jbehave-scm] jbehave-tutorial branch, master, updated. a3f52edd8db07a7799a28c3fae966f9302e06b3a
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-tutorial. The branch, master has been updated via a3f52edd8db07a7799a28c3fae966f9302e06b3a (commit) from af7bcb98387260efe0bc5666481f7cc9e4bd76d0 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit a3f52edd8db07a7799a28c3fae966f9302e06b3a Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Mon May 2 10:27:36 2011 +0200 Remove unneeded CompositeStepsFactory. --- Summary of changes: .../jbehave/tutorials/etsy/EtsyDotComStories.java | 14 +++--- 1 files changed, 3 insertions(+), 11 deletions(-) hooks/post-receive -- jbehave-tutorial hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-dev] [jira] Commented: (JBEHAVE-498) withRelativeDirectory appears to be broken
[
http://jira.codehaus.org/browse/JBEHAVE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=265426#action_265426
]
Mauro Talevi commented on JBEHAVE-498:
--
The relativeDirectory is the directory where the JBehave reporting outputs are
written to (defaults to jbehave), relative to the story builder code location
(defaults to CodeLocations.codeLocationFromPath(target/classes)).
If you change the relative directory and you're not using the Maven standard
layout, you'll probably need to set the code location accordingly, e.g.
CodeLocations.codeLocationFromPath(build/publish) and
withRelativeDirectory(story-reports), or combinations thereof.
You could also try seting the code location from the JUnitStories class:
CodeLocations.codeLocationFromClass(this.getClass());
withRelativeDirectory appears to be broken
--
Key: JBEHAVE-498
URL: http://jira.codehaus.org/browse/JBEHAVE-498
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: web-3.3
Environment: Linux. Jdk6
Reporter: Derek Clarkson
I'm working in a non maven environment. I attempted to set the output
directory for reports as follows
public static class MyReportBuilder extends StoryReporterBuilder {
public MyReportBuilder() {
super();
this.withRelativeDirectory(../build/publish/story-reports);
this.withFormats(CONSOLE, HTML, XML);
}
}
Upon running the JUnits I get the following:
org.jbehave.core.reporters.FilePrintStreamFactory$PrintStreamCreationFailed:
Failed to create print stream for file
/home/derek/workspace/smsManagerGit/target/../build/publish/story-reports/BeforeStories.html
at
org.jbehave.core.reporters.FilePrintStreamFactory.createPrintStream(FilePrintStreamFactory.java:39)
at
org.jbehave.core.reporters.Format$4.createStoryReporter(Format.java:43)
at
org.jbehave.core.reporters.StoryReporterBuilder.reporterFor(StoryReporterBuilder.java:310)
at
org.jbehave.core.reporters.StoryReporterBuilder.build(StoryReporterBuilder.java:285)
at
org.jbehave.core.configuration.Configuration.storyReporter(Configuration.java:200)
at
org.jbehave.core.embedder.StoryRunner.runBeforeOrAfterStories(StoryRunner.java:58)
at
org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:209)
at
au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder.run(AnnotatedStoryEmbedder.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: java.io.FileNotFoundException:
/home/derek/workspace/smsManagerGit/target/../build/publish/story-reports/BeforeStories.html
(No such file or directory)
at
[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.3.1-10-g8d988e7
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-web. The branch, master has been updated via 8d988e7de3cf60fde5bcf2f1d8a0809266c7e6d2 (commit) from a2cfea18b000b9f604307f297beca2976e94e59e (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 8d988e7de3cf60fde5bcf2f1d8a0809266c7e6d2 Author: Paul Hammant p...@hammant.org Date: Mon May 2 08:35:56 2011 -0500 tweak the LazyWebDriver logic to allow to replacement with non-lazy later --- Summary of changes: .../web/selenium/PerStoryWebDriverSteps.java |4 +++ .../org/jbehave/web/selenium/WebDriverPage.java| 28 +-- 2 files changed, 29 insertions(+), 3 deletions(-) hooks/post-receive -- jbehave-web hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-16-gef90072
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-core. The branch, master has been updated via ef9007230364debe162ec7849f6a95273ea4ac9c (commit) from 157f82b8a4c56ae0783096396cd7861c6f9d69a8 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit ef9007230364debe162ec7849f6a95273ea4ac9c Author: Paul Hammant p...@hammant.org Date: Mon May 2 10:04:25 2011 -0500 upgrade pico dep again --- Summary of changes: jbehave-pico/pom.xml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- jbehave-core hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-dev] [jira] Created: (JBEHAVE-499) Rename run-with-annotated-embedder goal to run-stories-with-annotated-embedder
Rename run-with-annotated-embedder goal to run-stories-with-annotated-embedder -- Key: JBEHAVE-499 URL: http://jira.codehaus.org/browse/JBEHAVE-499 Project: JBehave Issue Type: Improvement Components: Maven Plugin Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.4 The goal name is inconsistent with the other goal names. For backward compat, we can keep the previous goal name. -- 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
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-19-gfe8a9d9
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project jbehave-core.
The branch, master has been updated
via fe8a9d9b4a1d616e48d778fb7f38e5174718e6e3 (commit)
from 385f03407c6851e5e217fb51a9e7d0ee4b68ed74 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
commit fe8a9d9b4a1d616e48d778fb7f38e5174718e6e3
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date: Mon May 2 22:24:26 2011 +0200
JBEHAVE-499: Renamed maven goal to run-stories-with-annotated-embedder.
Previous goal run-with-annotated-embedder kept for backward compat but
deprecated. Fixed configuration of trader-annotations examples.
---
Summary of changes:
examples/trader-annotations/pom.xml|4 ++--
...derRunner.java = TraderAnnotatedEmbedder.java} | 17 +
.../annotations/TraderAnnotatedPathRunner.java |5 +++--
.../RunStoriesWithAnnotatedEmbedderRunner.java |4 ++--
.../mojo/RunWithAnnotatedEmbedderRunner.java | 10 ++
5 files changed, 26 insertions(+), 14 deletions(-)
rename
examples/trader-annotations/src/main/java/org/jbehave/examples/trader/annotations/{TraderAnnotatedEmbedderRunner.java
= TraderAnnotatedEmbedder.java} (84%)
create mode 100644
jbehave-maven-plugin/src/main/java/org/jbehave/mojo/RunWithAnnotatedEmbedderRunner.java
hooks/post-receive
--
jbehave-core
hr/
p
To unsubscribe from this list please visit:
/p
p
a
href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-dev] [jira] Resolved: (JBEHAVE-499) Rename run-with-annotated-embedder goal to run-stories-with-annotated-embedder
[ http://jira.codehaus.org/browse/JBEHAVE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-499. -- Resolution: Fixed Rename run-with-annotated-embedder goal to run-stories-with-annotated-embedder -- Key: JBEHAVE-499 URL: http://jira.codehaus.org/browse/JBEHAVE-499 Project: JBehave Issue Type: Improvement Components: Maven Plugin Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.4 The goal name is inconsistent with the other goal names. For backward compat, we can keep the previous goal name. -- 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
[jbehave-dev] [jira] Updated: (JBEHAVE-149) Support loading of stories from ODT format
[ http://jira.codehaus.org/browse/JBEHAVE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bart De Neuter updated JBEHAVE-149: --- Attachment: jbehave-odf-with-table.zip Mauro, I made some adjustments in order to use a real odt table in the text document. In that sense you can specify the example table with a nice layout. I attached the changes I made to your code. Support loading of stories from ODT format -- Key: JBEHAVE-149 URL: http://jira.codehaus.org/browse/JBEHAVE-149 Project: JBehave Issue Type: New Feature Components: ODF Support Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4 Attachments: jbehave-odf-with-table.zip As a BA I want to be able to write my story in a ODT format -- 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
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-22-gd8714b9
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project jbehave-core.
The branch, master has been updated
via d8714b969821765c76c4ae4075f8cab6022a78a7 (commit)
via 408d68606d0bea90c1e6ae0f9d788bd68075f914 (commit)
from ab07131a5370e82577d32bb5697df84192604fbc (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
commit d8714b969821765c76c4ae4075f8cab6022a78a7
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date: Tue May 3 00:09:09 2011 +0200
Encapsulated all UI controls in single class WindowsControl.
commit 408d68606d0bea90c1e6ae0f9d788bd68075f914
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date: Mon May 2 23:59:47 2011 +0200
More standard layout.
---
Summary of changes:
.../{util = }/NoughtsAndCrossesStory.java |3 ++-
.../steps/BeforeAndAfterSteps.java |2 +-
.../noughtsandcrosses/steps/GridSteps.java | 15 +--
.../noughtsandcrosses/steps/LolCatzSteps.java | 17 ++---
.../stories/PlayersCanHazTurns.java|6 +++---
.../stories/PlayersCanTakeTurns.java |2 +-
.../stories/TheGridStartsEmpty.java|2 +-
.../noughtsandcrosses/stories/ThreeInARowWins.java |2 +-
.../{util = ui}/WindowControl.java|8 +++-
.../util = resources/i18n}/keywords_lc.properties |0
10 files changed, 27 insertions(+), 30 deletions(-)
rename
examples/noughtsandcrosses/src/test/java/com/lunivore/noughtsandcrosses/{util
= }/NoughtsAndCrossesStory.java (93%)
rename
examples/noughtsandcrosses/src/test/java/com/lunivore/noughtsandcrosses/{util
= ui}/WindowControl.java (69%)
rename
examples/noughtsandcrosses/src/test/{java/com/lunivore/noughtsandcrosses/util
= resources/i18n}/keywords_lc.properties (100%)
hooks/post-receive
--
jbehave-core
hr/
p
To unsubscribe from this list please visit:
/p
p
a
href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-23-gb33f384
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-core. The branch, master has been updated via b33f384ba622e4ba469a482f67ce01a5f76f35eb (commit) from d8714b969821765c76c4ae4075f8cab6022a78a7 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit b33f384ba622e4ba469a482f67ce01a5f76f35eb Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Tue May 3 00:13:02 2011 +0200 Updated build notes. --- Summary of changes: distribution/src/site/content/building-source.html |5 - examples/noughtsandcrosses/README.txt |3 --- 2 files changed, 0 insertions(+), 8 deletions(-) delete mode 100644 examples/noughtsandcrosses/README.txt hooks/post-receive -- jbehave-core hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-24-gd1d8711
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-core. The branch, master has been updated via d1d87116cc35b5b222ca7cf83a71ebdb73d5f34f (commit) from b33f384ba622e4ba469a482f67ce01a5f76f35eb (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit d1d87116cc35b5b222ca7cf83a71ebdb73d5f34f Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Tue May 3 01:10:04 2011 +0200 JBEHAVE-500: AnnotatedEmbedderRunner now read from @RunWith annotation when running in CLI. --- Summary of changes: examples/trader-annotations/pom.xml|1 - .../java/org/jbehave/ant/AbstractEmbedderTask.java |3 +- .../ant/RunStoriesWithAnnotatedEmbedderRunner.java |4 +- .../org/jbehave/ant/EmbedderTaskBehaviour.java | 26 .../java/org/jbehave/core/embedder/Embedder.java | 58 ++--- .../jbehave/core/junit/AnnotatedEmbedderUtils.java | 69 .../jbehave/core/embedder/EmbedderBehaviour.java | 16 ++--- .../org/jbehave/mojo/AbstractEmbedderMojo.java |3 +- .../RunStoriesWithAnnotatedEmbedderRunner.java |4 +- .../org/jbehave/mojo/EmbedderMojoBehaviour.java| 26 10 files changed, 115 insertions(+), 95 deletions(-) create mode 100644 jbehave-core/src/main/java/org/jbehave/core/junit/AnnotatedEmbedderUtils.java hooks/post-receive -- jbehave-core hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-26-gee019c5
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-core. The branch, master has been updated via ee019c5a5fd128d607d8bd84aa961ae3dea77981 (commit) via 19036103d3d3ef7e1ca6a85ba3dc874737c8e83d (commit) from d1d87116cc35b5b222ca7cf83a71ebdb73d5f34f (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit ee019c5a5fd128d607d8bd84aa961ae3dea77981 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Tue May 3 01:16:58 2011 +0200 Removed file added by mistake. commit 19036103d3d3ef7e1ca6a85ba3dc874737c8e83d Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Tue May 3 01:16:17 2011 +0200 JBEHAVE-500: Run both annotated embedders in the example. --- Summary of changes: examples/trader-annotations/pom.xml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- jbehave-core hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-27-g8fcc32a
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-core. The branch, master has been updated via 8fcc32a910f0cc4db90195faf17c14aa4732dba2 (commit) from ee019c5a5fd128d607d8bd84aa961ae3dea77981 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 8fcc32a910f0cc4db90195faf17c14aa4732dba2 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Tue May 3 01:20:03 2011 +0200 JBEHAVE-500: Removed obsolete property from docs. --- Summary of changes: distribution/src/site/content/ant-tasks.html |2 -- distribution/src/site/content/maven-goals.html |2 -- 2 files changed, 0 insertions(+), 4 deletions(-) hooks/post-receive -- jbehave-core hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-28-g557b4a9
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project jbehave-core. The branch, master has been updated via 557b4a9b317add9165f25950ec66ed757bf902b2 (commit) from 8fcc32a910f0cc4db90195faf17c14aa4732dba2 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 557b4a9b317add9165f25950ec66ed757bf902b2 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Tue May 3 01:26:05 2011 +0200 JBEHAVE-149: Applied patch from Bart De Neuter. --- Summary of changes: .../java/org/jbehave/core/io/odf/OdfUtils.java | 70 +++ .../jbehave/core/io/odf/OdtLoaderBehaviour.java| 68 .../core/io/odf/stories/a_story_with_table.odt | Bin 0 - 11376 bytes 3 files changed, 96 insertions(+), 42 deletions(-) create mode 100644 jbehave-odf/src/test/java/org/jbehave/core/io/odf/stories/a_story_with_table.odt hooks/post-receive -- jbehave-core hr/ p To unsubscribe from this list please visit: /p p a href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a
[jbehave-dev] [jira] Commented: (JBEHAVE-149) Support loading of stories from ODT format
[ http://jira.codehaus.org/browse/JBEHAVE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=265516#action_265516 ] Mauro Talevi commented on JBEHAVE-149: -- Thanks, Bart. Patch applied. Support loading of stories from ODT format -- Key: JBEHAVE-149 URL: http://jira.codehaus.org/browse/JBEHAVE-149 Project: JBehave Issue Type: New Feature Components: ODF Support Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4 Attachments: jbehave-odf-with-table.zip As a BA I want to be able to write my story in a ODT format -- 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
[jbehave-dev] [jira] Commented: (JBEHAVE-498) withRelativeDirectory appears to be broken
[
http://jira.codehaus.org/browse/JBEHAVE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=265520#action_265520
]
Derek Clarkson commented on JBEHAVE-498:
Thanks for getting back to me so fast.
I've now tried:
this.withCodeLocation(CodeLocations.codeLocationFromPath(build/publish));
this.withRelativeDirectory(story-reports);
Which almost works. It creates the files in build/story-reports. I don't know
why it's ignoring the publish directory.
Just done some experimenting. It seems that you have to put in one more
directory level than you want to use. ie. build/publish maps to build,
build/publish/x maps to build/publish
So there still appears to be a bug in that it is not correctly assembling the
output path from the code location.
Secondly I'd like to request that StoryReportBuilder.withCodeLocation(...) be
renamed to StoryReportBuilder.withReportLocation(...). Calling it
withCodeLocation is anything but intuitive and the whole reason I wasted
several hours trying to figure out how to do this before posting the bug
report. In addition, I don't see the need for a separation of the location and
relative directory. It just adds to the confusion.
withRelativeDirectory appears to be broken
--
Key: JBEHAVE-498
URL: http://jira.codehaus.org/browse/JBEHAVE-498
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: web-3.3
Environment: Linux. Jdk6
Reporter: Derek Clarkson
I'm working in a non maven environment. I attempted to set the output
directory for reports as follows
public static class MyReportBuilder extends StoryReporterBuilder {
public MyReportBuilder() {
super();
this.withRelativeDirectory(../build/publish/story-reports);
this.withFormats(CONSOLE, HTML, XML);
}
}
Upon running the JUnits I get the following:
org.jbehave.core.reporters.FilePrintStreamFactory$PrintStreamCreationFailed:
Failed to create print stream for file
/home/derek/workspace/smsManagerGit/target/../build/publish/story-reports/BeforeStories.html
at
org.jbehave.core.reporters.FilePrintStreamFactory.createPrintStream(FilePrintStreamFactory.java:39)
at
org.jbehave.core.reporters.Format$4.createStoryReporter(Format.java:43)
at
org.jbehave.core.reporters.StoryReporterBuilder.reporterFor(StoryReporterBuilder.java:310)
at
org.jbehave.core.reporters.StoryReporterBuilder.build(StoryReporterBuilder.java:285)
at
org.jbehave.core.configuration.Configuration.storyReporter(Configuration.java:200)
at
org.jbehave.core.embedder.StoryRunner.runBeforeOrAfterStories(StoryRunner.java:58)
at
org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:209)
at
au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder.run(AnnotatedStoryEmbedder.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
at
org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at
[jbehave-dev] [jira] Created: (JBEHAVE-501) Report stying not being generated
Report stying not being generated
-
Key: JBEHAVE-501
URL: http://jira.codehaus.org/browse/JBEHAVE-501
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.3.2
Environment: Ant, Eclipse, JDK6
Reporter: Derek Clarkson
I am using this report builder definition in a annotation setup as per the
JBehave website documentation:
public static class MyReportBuilder extends StoryReporterBuilder {
public MyReportBuilder() {
super();
this.withCodeLocation(CodeLocations.codeLocationFromPath(build/publish/x));
this.withRelativeDirectory(story-reports);
this.withDefaultFormats();
this.withFormats(CONSOLE, HTML);
}
}
The reports are being generated in the view directory, however there are no
images, css or javascript being generated even though the html refers to them.
I've scoured the web site documentation which suggests that they should be and
tells you how to turn them off, but not what to do if they are not there.
--
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
[jbehave-dev] [jira] Created: (JBEHAVE-502) Add installation instructions to website documentation
Add installation instructions to website documentation -- Key: JBEHAVE-502 URL: http://jira.codehaus.org/browse/JBEHAVE-502 Project: JBehave Issue Type: Improvement Components: Core Reporter: Derek Clarkson I've been scouring the site for a couple of days trying to figure out what I needed to install and where. I'm not using maven. The website doesn't give any idea of how to setup JBehave when not in a maven environment. So I'm having to do it by reverse engineering the maven pom. The first problem was to trying and figure out what to download. The linked download file is only of use in a maven world. So I had to start downloaded by surfing the online repos. So I'd suggest that the raw jars and zips should also be linked for download from the main site. The second issue was what to unzip, etc and suggested directories. Again the documentation takes a it will just work approach, which it doesn't. So instructions are needed here to. -- 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
[jbehave-dev] [jira] Created: (JBEHAVE-503) maps.html not being generated
maps.html not being generated - Key: JBEHAVE-503 URL: http://jira.codehaus.org/browse/JBEHAVE-503 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.3.2 Reporter: Derek Clarkson The generated reports include a link to a maps.html. But the file is not generated. How do I turn it on or remove the link? -- 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
[jbehave-dev] [jira] Commented: (JBEHAVE-501) Report stying not being generated
[
http://jira.codehaus.org/browse/JBEHAVE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=265529#action_265529
]
Derek Clarkson commented on JBEHAVE-501:
OK, I eventually managed to locate a zip file of the css, javascript and images
on
https://nexus.codehaus.org/content/repositories/releases/org/jbehave/site/jbehave-site-resources/
however it is only 3.1.1 and the jbehave.css file is a different name to
generated html which expects jbehave-core.css. Thats in the core jar file but
is not extracted by the reports.
I extracted the zip and set it as a source folder in eclipse with a output
folder that matches my reports directories. So that got most of the bits in the
correct place.
Either there is an easier (non-maven) way of doing this or stuff is missing
from the downloads and documentation sections of the JBehave website.
Report stying not being generated
-
Key: JBEHAVE-501
URL: http://jira.codehaus.org/browse/JBEHAVE-501
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.3.2
Environment: Ant, Eclipse, JDK6
Reporter: Derek Clarkson
I am using this report builder definition in a annotation setup as per the
JBehave website documentation:
public static class MyReportBuilder extends StoryReporterBuilder {
public MyReportBuilder() {
super();
this.withCodeLocation(CodeLocations.codeLocationFromPath(build/publish/x));
this.withRelativeDirectory(story-reports);
this.withDefaultFormats();
this.withFormats(CONSOLE, HTML);
}
}
The reports are being generated in the view directory, however there are no
images, css or javascript being generated even though the html refers to
them. I've scoured the web site documentation which suggests that they should
be and tells you how to turn them off, but not what to do if they are not
there.
--
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
[jbehave-dev] [jira] Commented: (JBEHAVE-502) Add installation instructions to website documentation
[ http://jira.codehaus.org/browse/JBEHAVE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=265534#action_265534 ] Cristiano Gavião commented on JBEHAVE-502: -- Hi Derek, I'm curious... What is the problem of maven for you ? I'm trying to imagine myself on the situation of have to download every jbehave dependency by hand but I really can't. :-) Do you really prefer to download and control the version of each dependency by hand ? Add installation instructions to website documentation -- Key: JBEHAVE-502 URL: http://jira.codehaus.org/browse/JBEHAVE-502 Project: JBehave Issue Type: Improvement Components: Core Reporter: Derek Clarkson I've been scouring the site for a couple of days trying to figure out what I needed to install and where. I'm not using maven. The website doesn't give any idea of how to setup JBehave when not in a maven environment. So I'm having to do it by reverse engineering the maven pom. The first problem was to trying and figure out what to download. The linked download file is only of use in a maven world. So I had to start downloaded by surfing the online repos. So I'd suggest that the raw jars and zips should also be linked for download from the main site. The second issue was what to unzip, etc and suggested directories. Again the documentation takes a it will just work approach, which it doesn't. So instructions are needed here to. -- 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
