[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-4-13-gb6c573b
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 b6c573ba8a7d31076f77be770af0b09fe01cd247 (commit) from bebac806c4ff3ca3c97ce03163dac684f199ebe0 (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 b6c573ba8a7d31076f77be770af0b09fe01cd247 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Sun May 15 10:26:57 2011 +0100 JBEHAVE-476: Added maven.archetype.version property. --- Summary of changes: archetypes/pom.xml |5 +++-- 1 files changed, 3 insertions(+), 2 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-4-14-g799edc9
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 799edc92c7b14e588bdbdbb52dac9371fb46a114 (commit) from b6c573ba8a7d31076f77be770af0b09fe01cd247 (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 799edc92c7b14e588bdbdbb52dac9371fb46a114 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Sun May 15 10:46:59 2011 +0100 JBEHAVE-476: Only filter archetype-metadata.xml to prevent premature replacement of GAV coordinates in the archetype pom.xml. --- Summary of changes: archetypes/pom.xml | 10 ++ 1 files changed, 10 insertions(+), 0 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
Re: [jbehave-dev] A request to improve adoption
Hi Liz,
to copy all the jars, and not build the source, you don't do any mvn
install. You can copy the dependency via the Ant task:
- cd lib
- ant
The Ant build.xml uses the pom.xml simply to know which jars to copy.
Cheers
On 15/05/2011 17:04, Elizabeth Keogh wrote:
Hi Mauro,
I did this (using Windows 7 64-bit, Maven 2.2.1, Java 1.6.0_25):
- Download JBehave binary 3.3.2 and unzip
- Copy 3.3.2 settings.xml from source to lib dir
- cd lib folder
- Run mvn -s settings.xml clean install
I still get this error:
[INFO] Executed tasks
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] [xsite:run {execution: default}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to run xsite
Something else I'm missing?
Cheers,
Liz.
On Fri, May 13, 2011 at 7:22 AM, Mauro Talevi
mauro.tal...@aquilonia.org wrote:
Hi,
the point of using Maven is that you don't need to build the jars, these are
already available on Maven Central and will be automatically downloaded when
you declare them in your pom.xml:
http://repo2.maven.org/maven2/org/jbehave/jbehave-core/
If you don't use Maven, the binary distribution includes an Ant build.xml to
allow you to copy all dependencies locally:
http://jbehave.org/reference/preview/dependencies.html
$cd lib
$ant copy-dependencies
If you are trying to build from source then you can find the build
instructions:
http://jbehave.org/reference/preview/building-source.html
Also, current build requires Maven 2.2.x and the site part has not been
fully migrated to 3.0.x (which is the major non-compat of Maven 2-3).
Cheers
On 13/05/2011 05:32, M CHILDS wrote:
Could the binary release (I'm using 3.3.2) include a fully built jar file? I
think this will improve the chances of people checking out and adopting
jbehave.
I request this because I've spent several hours and haven't gotten the
binary release to build into something I can drop into my project. Each
issue requires me to learn something brand new, so it is very frustrating,
because all I want to do is start using jbehave.
The remaining information is for troubleshooting. I'm not sure this is the
correct list for troubleshooting, but I've included it in case it is.
I am brand new to maven and jbehave. I ran this command under release/lib:
mvn clean install
The first issue is the weld-se 1.1.0Final jar not being available in the
repositories by default (so I added the repo). Known issue.
The second is unsolved, and is this:
[ERROR] Failed to execute goal org.codehaus.xsite:xsite-maven-plugin:1.2:run
(default) on project jbehave-distribution: Failed to run xsite:
NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.codehaus.xsite:xsite-maven-plugin:1.2:run (default) on project
jbehave-distribution: Failed to run xsite
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to run
xsite
at
org.codehaus.xsite.mojo.XSiteRunMojo.execute(XSiteRunMojo.java:84)
at
[jbehave-dev] [jira] Commented: (JBEHAVE-390) browser not closing when done by @AfterStories
[
http://jira.codehaus.org/browse/JBEHAVE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=267063#action_267063
]
Ivan Vanyushkin commented on JBEHAVE-390:
-
I have this issue with runner:
{code}
maven-surefire-plugin = JUnitStories.run() = embedder.runStoriesAsPaths()
{code}
I also have this issue with assertion exceptions: {{java.lang.AssertionError}}.
I don't have this issue with runner:
{code}
jbehave-maven-plugin:run-stories-as-embeddables
{code}
with same code.
browser not closing when done by @AfterStories
--
Key: JBEHAVE-390
URL: http://jira.codehaus.org/browse/JBEHAVE-390
Project: JBehave
Issue Type: Bug
Components: Web Selenium
Affects Versions: web-3.1.1
Reporter: Paul Hammant
Fix For: web-3.x
PerStoriesWebDriverSteps has a before and after stories. If there's a
WebDriver thrown exception (a derivative of RuntimeE), then the @AfterStores
annotated method is not called . and as such the browser frame is not
closed.
--
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] Issue Comment Edited: (JBEHAVE-390) browser not closing when done by @AfterStories
[
http://jira.codehaus.org/browse/JBEHAVE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=267063#action_267063
]
Ivan Vanyushkin edited comment on JBEHAVE-390 at 5/15/11 12:01 PM:
---
I have this issue with runner:
{code}
maven-surefire-plugin = JUnitStories.run() = embedder.runStoriesAsPaths()
{code}
I also have this issue with assertion exceptions: {{java.lang.AssertionError}}.
I don't have this issue with runner:
{code}
jbehave-maven-plugin:run-stories-as-embeddables
{code}
with same code.
Maybe related issue: JBEHAVE-465.
was (Author: vanav):
I have this issue with runner:
{code}
maven-surefire-plugin = JUnitStories.run() = embedder.runStoriesAsPaths()
{code}
I also have this issue with assertion exceptions: {{java.lang.AssertionError}}.
I don't have this issue with runner:
{code}
jbehave-maven-plugin:run-stories-as-embeddables
{code}
with same code.
browser not closing when done by @AfterStories
--
Key: JBEHAVE-390
URL: http://jira.codehaus.org/browse/JBEHAVE-390
Project: JBehave
Issue Type: Bug
Components: Web Selenium
Affects Versions: web-3.1.1
Reporter: Paul Hammant
Fix For: web-3.x
PerStoriesWebDriverSteps has a before and after stories. If there's a
WebDriver thrown exception (a derivative of RuntimeE), then the @AfterStores
annotated method is not called . and as such the browser frame is not
closed.
--
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-498) withRelativeDirectory appears to be broken
[
http://jira.codehaus.org/browse/JBEHAVE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-498:
-
Fix Version/s: (was: 3.4)
3.x
withRelativeDirectory appears to be broken
--
Key: JBEHAVE-498
URL: http://jira.codehaus.org/browse/JBEHAVE-498
Project: JBehave
Issue Type: Bug
Components: Core
Environment: Linux. Jdk6
Reporter: Derek Clarkson
Fix For: 3.x
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 java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.init(FileOutputStream.java:179)
at
org.jbehave.core.reporters.FilePrintStreamFactory$FilePrintStream.init(FilePrintStreamFactory.java:137)
at
org.jbehave.core.reporters.FilePrintStreamFactory.createPrintStream(FilePrintStreamFactory.java:37)
... 31 more
Commenting out the withRelativeDirectory() method and everything works just
fine.
--
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
-
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-4-16-g1f323ff
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 1f323ffed5254219835ae8ede7023c8cbfea45c8 (commit) via ea7fdfdb5ab9f6250c6e99e41f67ac82663e9d01 (commit) from 799edc92c7b14e588bdbdbb52dac9371fb46a114 (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 1f323ffed5254219835ae8ede7023c8cbfea45c8 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Sun May 15 19:02:52 2011 +0100 Updated release notes. commit ea7fdfdb5ab9f6250c6e99e41f67ac82663e9d01 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Sun May 15 18:49:32 2011 +0100 JBEHAVE-476: Changed required property names to allow proper template replacement in pom.xml --- Summary of changes: .../META-INF/maven/archetype-metadata.xml |4 ++-- .../src/main/resources/archetype-resources/pom.xml |2 ++ .../META-INF/maven/archetype-metadata.xml |4 ++-- .../src/main/resources/archetype-resources/pom.xml |2 ++ .../META-INF/maven/archetype-metadata.xml |4 ++-- .../src/main/resources/archetype-resources/pom.xml |2 ++ .../META-INF/maven/archetype-metadata.xml |4 ++-- .../src/main/resources/archetype-resources/pom.xml |2 ++ .../META-INF/maven/archetype-metadata.xml |4 ++-- .../src/main/resources/archetype-resources/pom.xml |2 ++ .../resources/projects/sample/archetype.properties |4 ++-- distribution/src/site/content/release-notes.html | 12 ++-- 12 files changed, 32 insertions(+), 14 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-4-17-gbfb6f3a
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 bfb6f3a741adfe7ce125e49b4416905fd588fd18 (commit) from 1f323ffed5254219835ae8ede7023c8cbfea45c8 (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 bfb6f3a741adfe7ce125e49b4416905fd588fd18 Author: Mauro Talevi mauro.tal...@aquilonia.org Date: Sun May 15 19:29:21 2011 +0100 JBEHAVE-467: Add test for EmbedderMonitorDecorator. --- Summary of changes: .../core/embedder/EmbedderMonitorBehaviour.java| 102 +++- 1 files changed, 97 insertions(+), 5 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
