[jbehave-dev] [jira] (JBEHAVE-679) Update EBNF grammar

2011-12-20 Thread Olmo Rigolo (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286369#comment-286369 ] Olmo Rigolo commented on JBEHAVE-679: - Nothing changed here: http://jbehave.org/reference/stab

[jbehave-dev] [jira] (JBEHAVE-679) Update EBNF grammar

2011-12-20 Thread Mauro Talevi (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286374#comment-286374 ] Mauro Talevi commented on JBEHAVE-679: -- It will once we release 3.6 stable (not beta)

[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.4.3-10-g9bb6b88

2011-12-20 Thread git
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 9bb6b88bd11f95575fa50993eb6ef739b05a6ffd (commit) from 09bf8458fe91d6a5

[jbehave-dev] [jira] (JBEHAVE-681) Pending steps methods leave invalid chars in the method name

2011-12-20 Thread Alexander Lehmann (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286381#comment-286381 ] Alexander Lehmann commented on JBEHAVE-681: --- (I can create a patch, it was just getting

[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.4.3-11-ge3746f9

2011-12-20 Thread git
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 e3746f9e1a9407ac3d3f2a67979d9dbba952e436 (commit) from 9bb6b88bd11f9557

Re: [jbehave-dev] Can we configure the runner output?

2011-12-20 Thread Olmo Rigolo
Hi Mauro, thanks for your reply. Could you provide an example? Thanks, Olmo On 19 December 2011 15:47, Mauro Talevi wrote: > Providing your own impl of EmbedderMonitor. > On Mon Dec 19 15:46:48 2011, Olmo Rigolo wrote: > >> Hi, >> >> Every time I run a story, within the process of the storyrun

[jbehave-dev] [jira] (JBEHAVE-234) Improve JUnit integration

2011-12-20 Thread Olmo Rigolo (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=286413#comment-286413 ] Olmo Rigolo commented on JBEHAVE-234: - Hi Mauro, could you please provide a better example ho

[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.6-beta-1-4-g719e5cc

2011-12-20 Thread git
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 719e5cc36a30e70c56242cadba64e4a1535fd0cb (commit) from f5b4b8b15da9bb6

[jbehave-dev] [jira] (JBEHAVE-674) HTML decoration marks parameters twice

2011-12-20 Thread Mauro Talevi (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-674. -- Resolution: Fixed Applied patch. Added unit test to reproduce behaviour. > HTML d

Re: [jbehave-dev] Can we configure the runner output?

2011-12-20 Thread Mauro Talevi
public ThreadsStories() { Embedder embedder = configuredEmbedder(); embedder.useEmbedderMonitor(new PrintStreamEmbedderMonitor(){ @Override public void runningStory(String path) { print("Your message"); } }); / // other

[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.6-beta-1-5-g5cd5b4d

2011-12-20 Thread git
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 5cd5b4d75a4cd9b7cf7cf350c069b3610da23dd2 (commit) from 719e5cc36a30e70

[jbehave-dev] [jira] (JBEHAVE-681) Pending steps methods leave invalid chars in the method name

2011-12-20 Thread Mauro Talevi (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-681. -- Resolution: Fixed Fix Version/s: 3.6 Assignee: Mauro Talevi > Pending steps met

Re: [jbehave-dev] Can we configure the runner output?

2011-12-20 Thread Olmo Rigolo
Hi Mauro, thanks. How couldn't I find it out myself? Little by little I begin to understand the implementation and the power of JBehave. I think it is very good and makes JBehave so powerful, that you can configure it like you want. But at the beginning it's kind of difficult if there are more th

[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.4.3-13-ga8aed45

2011-12-20 Thread git
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 a8aed45205257cc1c9a29d5576b18a58118df0fc (commit) via 119a6d86c67a02b3

[jbehave-dev] [jira] (JBEHAVE-682) SauceLabs can cancel jobs on their stack (timeouts). StoryReporter/ScreenShotter should be more robust when encountering that

2011-12-20 Thread Paul Hammant (JIRA)
Paul Hammant created JBEHAVE-682: Summary: SauceLabs can cancel jobs on their stack (timeouts). StoryReporter/ScreenShotter should be more robust when encountering that Key: JBEHAVE-682 URL: https://jira.codehaus

[jbehave-dev] [jira] (JBEHAVE-682) SauceLabs can cancel jobs on their stack (timeouts). StoryReporter/ScreenShotter should be more robust when encountering that

2011-12-20 Thread Paul Hammant (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant resolved JBEHAVE-682. -- Resolution: Fixed > SauceLabs can cancel jobs on their stack (timeouts). > StoryReporter/Scre

[jbehave-dev] [jira] (JBEHAVE-678) Smarter setting of browser version on SauceLabs

2011-12-20 Thread Paul Hammant (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant resolved JBEHAVE-678. -- Resolution: Fixed > Smarter setting of browser version on SauceLabs > -

[jbehave-dev] [jira] (JBEHAVE-677) Allow Wrapping of Selenium2 CommandExecutor for Instrumentation purposes

2011-12-20 Thread Paul Hammant (JIRA)
[ https://jira.codehaus.org/browse/JBEHAVE-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant resolved JBEHAVE-677. -- Resolution: Fixed > Allow Wrapping of Selenium2 CommandExecutor for Instrumentation purposes >