[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-7-g07ce3c3

2011-05-28 Thread git version control 
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  07ce3c326fac636b0f23c457b0a3c1b8f4b545f0 (commit)
  from  03a5b790047c1321b0de3b6f16495d57bc94e5d3 (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 07ce3c326fac636b0f23c457b0a3c1b8f4b545f0
Author: Mauro Talevi 
Date:   Sat May 28 10:09:18 2011 +0200

Fixed doc link

---

Summary of changes:
 distribution/src/site/content/multi-threading.html |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
jbehave-core



To unsubscribe from this list please visit:


http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email

[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-6-g03a5b79

2011-05-28 Thread git version control 
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  03a5b790047c1321b0de3b6f16495d57bc94e5d3 (commit)
  from  06d60f60ff5713e018c35a5f67f8eb10e10e8531 (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 03a5b790047c1321b0de3b6f16495d57bc94e5d3
Author: Mauro Talevi 
Date:   Sat May 28 09:33:50 2011 +0200

Updated release notes.

---

Summary of changes:
 distribution/src/site/content/release-notes.html |   19 +++
 1 files changed, 19 insertions(+), 0 deletions(-)


hooks/post-receive
-- 
jbehave-core



To unsubscribe from this list please visit:


http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email

[jbehave-dev] [jira] Updated: (JBEHAVE-520) StoryRunner failure strategy is not set when running before or after stories steps in multiple threads

2011-05-28 Thread Mauro Talevi (JIRA) 

 [ 
http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mauro Talevi updated JBEHAVE-520:
-

Summary: StoryRunner failure strategy is not set when running before or 
after stories steps in multiple threads  (was: NPE in StoryRunner: 
currentStrategy is not set when running before or after stories steps)

> StoryRunner failure strategy is not set when running before or after stories 
> steps in multiple threads
> --
>
> Key: JBEHAVE-520
> URL: http://jira.codehaus.org/browse/JBEHAVE-520
> Project: JBehave
>  Issue Type: Bug
>  Components: Core
>Affects Versions: 3.4
> Environment: Windowx XP, mvn 3.0.3 and 2.2.1, jbehave 3.4
>Reporter: Maciej Madej
>Priority: Critical
> Fix For: 3.4.1
>
> Attachments: jbehave-after-before-bug.zip
>
>
> I got following exception when building attached project (mvn clean install):
> ---
> Test set: pl.mmadej.jbehave.JBehaveStoriesTest
> ---
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.562 sec <<< 
> FAILURE!
> [run_with_no_replacement.story](pl.mmadej.jbehave.JBehaveStoriesTest)  Time 
> elapsed: 0.343 sec  <<< ERROR!
> org.jbehave.core.embedder.Embedder$RunningStoriesFailed: Failures in running 
> before or after stories steps
>   at 
> org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:210)
>   at pl.mmadej.jbehave.JBehaveStoriesTest.run(JBehaveStoriesTest.java:99)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> Please investigate. This error happens with jbehave 3.4. When I'm using 3.3.2 
> everything looks ok. 
> Internally there is NPE in StoryRunner:76 --  
> currentStrategy.get().handleFailure(storyFailure.get());
> currentStrategy.get() returns null.
> Please investigate.
> Thanks in advance for your help

-- 
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