[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.0-rc1-8-g4e81865

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 4e818654018e713f7b4b1f074dd2a5d0b2355eec (commit) via 14a4f120d7baef27

[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235546#action_235546 ] Brian Repko commented on JBEHAVE-338: - we've already got the configuration around greedy vs non-

[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235544#action_235544 ] Mauro Talevi commented on JBEHAVE-338: -- Yes, it's essentially the pre-parsing concept proposed

[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235540#action_235540 ] Paul Hammant commented on JBEHAVE-338: -- Au contraire, we could regex for whitespace at the star

[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235538#action_235538 ] Mauro Talevi commented on JBEHAVE-338: -- The notification to users is the fact that the step is

[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235537#action_235537 ] Paul Hammant commented on JBEHAVE-338: -- If there' a reason for it - fine. The HTML output is in

[jbehave-dev] [jira] Updated: (JBEHAVE-337) Document how to configure jbehave-maven-plugin to be aware of log4j dependency

[ http://jira.codehaus.org/browse/JBEHAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-337: - Fix Version/s: 3.1 Issue Type: Task (was: Bug) Summary: Document how to configure jbe

[jbehave-dev] [jira] Updated: (JBEHAVE-339) HTML report numbers could be more tabular

[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-339: - Fix Version/s: 3.1 > HTML report numbers could be more tabular >

[jbehave-dev] [jira] Updated: (JBEHAVE-339) HTML report numbers could be more tabular

[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-339: - Description: guice.stories.simple_guice_example Scenarios: 1 (Failed: 0) Steps: 3 (Successful: 3

[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235534#action_235534 ] Mauro Talevi commented on JBEHAVE-338: -- Brian is quite right - this is not a regression, rather

[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235519#action_235519 ] Brian Repko commented on JBEHAVE-338: - I believe that this had to do with the change to support

[jbehave-dev] [jira] Created: (JBEHAVE-339) HTML report numbers could be more tabular

HTML report numbers could be more tabular -- Key: JBEHAVE-339 URL: http://jira.codehaus.org/browse/JBEHAVE-339 Project: JBehave Issue Type: Improvement Components: Core Affects Versions:

[jbehave-dev] [jira] Created: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3 - Key: JBEHAVE-338 URL: http://jira.codehaus.org/browse/JBEHAVE-338 Project: JBehave

[jbehave-dev] [jira] Commented: (JBEHAVE-337) jbehave-maven-plugin thows NoClassDefFoundError org/apache/log4j/Priority when maven project includes log4j dependency

[ http://jira.codehaus.org/browse/JBEHAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235499#action_235499 ] Mauro Talevi commented on JBEHAVE-337: -- Add dependency to plugin rather than the project (see e

[jbehave-dev] [jira] Created: (JBEHAVE-337) jbehave-maven-plugin thows NoClassDefFoundError org/apache/log4j/Priority when maven project includes log4j dependency

jbehave-maven-plugin thows NoClassDefFoundError org/apache/log4j/Priority when maven project includes log4j dependency -- Key: JBEHAVE-337 URL: htt

[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.0-rc1-5-gd71de63

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 d71de638951364621aff3394e243c23f423796b0 (commit) from 8bbf7544da93bc9a

[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.0-rc1-4-g8bbf754

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 8bbf7544da93bc9af68da74a9a0edd5b4e4b33a6 (commit) via ad8f6834c10b8da6