[jbehave-dev] [jira] Commented: (JBEHAVE-230) Add Narrative elements to Story parsing

[ http://jira.codehaus.org/browse/JBEHAVE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=210942#action_210942 ] Mauro Talevi commented on JBEHAVE-230: -- Added keyword-driven optional narrative elements to

[jbehave-dev] [jira] Resolved: (JBEHAVE-230) Add Narrative elements to Story parsing

[ http://jira.codehaus.org/browse/JBEHAVE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-230. -- Resolution: Fixed Add Narrative elements to Story parsing ---

[jbehave-dev] [jira] Assigned: (JBEHAVE-162) Need to be able to set order of steps for matching

[ http://jira.codehaus.org/browse/JBEHAVE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-162: Assignee: Mauro Talevi Need to be able to set order of steps for matching

[jbehave-dev] [jira] Resolved: (JBEHAVE-162) Need to be able to set order of steps for matching

[ http://jira.codehaus.org/browse/JBEHAVE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-162. -- Resolution: Fixed Need to be able to set order of steps for matching

[jbehave-dev] [jira] Commented: (JBEHAVE-162) Need to be able to set order of steps for matching

[ http://jira.codehaus.org/browse/JBEHAVE-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=210982#action_210982 ] Mauro Talevi commented on JBEHAVE-162: -- Added optional priority attribute to step method

[jbehave-dev] [jira] Commented: (JBEHAVE-216) Allow to indicate which is the weight of each StepsCandidate class used by a Scenario class to resolve duplicated methods.

[ http://jira.codehaus.org/browse/JBEHAVE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=210983#action_210983 ] Mauro Talevi commented on JBEHAVE-216: -- A solution is now provided by the ability to prioritise

[jbehave-dev] [jira] Reopened: (JBEHAVE-239) Add @BeforeStory and @AfterStory annotations in candidate steps

[ http://jira.codehaus.org/browse/JBEHAVE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-239: -- Add @BeforeStory and @AfterStory annotations in candidate steps

[jbehave-dev] [jira] Commented: (JBEHAVE-239) Add @BeforeStory and @AfterStory annotations in candidate steps

[ http://jira.codehaus.org/browse/JBEHAVE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=211581#action_211581 ] Mauro Talevi commented on JBEHAVE-239: -- Added uponEmbedded=[true|false] attribute to

[jbehave-dev] [jira] Resolved: (JBEHAVE-239) Add @BeforeStory and @AfterStory annotations in candidate steps

[ http://jira.codehaus.org/browse/JBEHAVE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-239. -- Resolution: Fixed Add @BeforeStory and @AfterStory annotations in candidate steps

[jbehave-dev] [jira] Reopened: (JBEHAVE-216) Allow to indicate which is the weight of each StepsCandidate class used by a Scenario class to resolve duplicated methods.

[ http://jira.codehaus.org/browse/JBEHAVE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-216: -- Rather than resolving it as Won't Fix, re-opening and descoping this features in case it does turn out

[jbehave-dev] [jira] Updated: (JBEHAVE-216) Allow to indicate which is the weight of each StepsCandidate class used by a Scenario class to resolve duplicated methods.

[ http://jira.codehaus.org/browse/JBEHAVE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-216: - Fix Version/s: (was: 2.5) Allow to indicate which is the weight of each StepsCandidate class

[jbehave-dev] [jira] Created: (JBEHAVE-245) Abstract scenarios should not be executed

Abstract scenarios should not be executed - Key: JBEHAVE-245 URL: http://jira.codehaus.org/browse/JBEHAVE-245 Project: JBehave Issue Type: Improvement Components: Ant extension, Maven Plugin

[jbehave-dev] [jira] Resolved: (JBEHAVE-245) Abstract scenarios should not be executed

[ http://jira.codehaus.org/browse/JBEHAVE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-245. -- Resolution: Fixed Abstract scenarios should not be executed

[jbehave-dev] [jira] Reopened: (JBEHAVE-250) onfiguration/ if missing for Maven/Ant needs better exception handling and console output

[ http://jira.codehaus.org/browse/JBEHAVE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-250: -- onfiguration/ if missing for Maven/Ant needs better exception handling and console output

[jbehave-dev] [jira] Updated: (JBEHAVE-250) Provide better exception handling when Maven/Ant fails with classloader injected

[ http://jira.codehaus.org/browse/JBEHAVE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-250: - Description: When Maven/Ant execution of a scenario with injected classloader, provide better

[jbehave-dev] [jira] Resolved: (JBEHAVE-250) Provide better exception handling when Maven/Ant fails with classloader injected

[ http://jira.codehaus.org/browse/JBEHAVE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-250. -- Resolution: Fixed Provide better exception handling when Maven/Ant fails with classloader

[jbehave-dev] [jira] Deleted: (JBEHAVE-249) Abstract scenario classes need should never be added to list of ones to instantiate regardless of include/exclude settings in Maven or Ant

[ http://jira.codehaus.org/browse/JBEHAVE-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi deleted JBEHAVE-249: - Abstract scenario classes need should never be added to list of ones to instantiate regardless of

[jbehave-dev] [jira] Resolved: (JBEHAVE-208) Ability to have comments in scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-208. -- Resolution: Duplicate Duplicate of JBEHAVE-163 Ability to have comments in scenarios

[jbehave-dev] [jira] Updated: (JBEHAVE-156) Allow resolution of multiple textual scenarios from a single Java scenario

[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-156: - Fix Version/s: 3.0 Issue Type: New Feature (was: Improvement) Allow resolution of multiple

[jbehave-dev] [jira] Updated: (JBEHAVE-247) jBehave should be more intelligent/flexible with regards to priortisation of steps

[ http://jira.codehaus.org/browse/JBEHAVE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-247: - Fix Version/s: 3.0 Issue Type: New Feature (was: Improvement) jBehave should be more

[jbehave-dev] [jira] Commented: (JBEHAVE-246) Improve terminology, the distinction between a story and a scenario

[ http://jira.codehaus.org/browse/JBEHAVE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=214659#action_214659 ] Mauro Talevi commented on JBEHAVE-246: -- A story is made of multiple scenarios, not the other

[jbehave-dev] [jira] Updated: (JBEHAVE-246) Improve terminology, the distinction between a story and a scenario

[ http://jira.codehaus.org/browse/JBEHAVE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-246: - Fix Version/s: 3.0 Improve terminology, the distinction between a story and a scenario

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

[ http://jira.codehaus.org/browse/JBEHAVE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-234: - Fix Version/s: 3.0 Improve JUnit integration - Key:

[jbehave-dev] [jira] Created: (JBEHAVE-252) Improve documentation on scenario and step configuration

Improve documentation on scenario and step configuration Key: JBEHAVE-252 URL: http://jira.codehaus.org/browse/JBEHAVE-252 Project: JBehave Issue Type: Improvement

[jbehave-dev] [jira] Created: (JBEHAVE-253) ClassLoader-aware Spring ApplicationContext factory

ClassLoader-aware Spring ApplicationContext factory --- Key: JBEHAVE-253 URL: http://jira.codehaus.org/browse/JBEHAVE-253 Project: JBehave Issue Type: Improvement Reporter: Mauro

[jbehave-dev] [jira] Resolved: (JBEHAVE-253) ClassLoader-aware Spring ApplicationContext factory

[ http://jira.codehaus.org/browse/JBEHAVE-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-253. -- Resolution: Fixed ClassLoader-aware Spring ApplicationContext factory

[jbehave-dev] [jira] Resolved: (JBEHAVE-252) Improve documentation on scenario and step configuration

[ http://jira.codehaus.org/browse/JBEHAVE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-252. -- Resolution: Fixed Improve documentation on scenario and step configuration

[jbehave-dev] [jira] Updated: (JBEHAVE-244) Step parameters should be converted just before the step executes (not when the scenario is parsed)

[ http://jira.codehaus.org/browse/JBEHAVE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-244: - Fix Version/s: (was: 2.6) 3.0 Step parameters should be converted just before

[jbehave-dev] [jira] Updated: (JBEHAVE-254) Review story/steps configuration

[ http://jira.codehaus.org/browse/JBEHAVE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-254: - Description: Story and steps configuration should be reviewed to maintain what worked well and

[jbehave-dev] [jira] Updated: (JBEHAVE-156) Allow running of multiple textual stories using a single Java RunnableStory

[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-156: - Comment: was deleted (was: Bumping out of 2.2 release until consensus is reached on how to approach

[jbehave-dev] [jira] Created: (JBEHAVE-255) Make column separator configurable in ExamplesTable

Make column separator configurable in ExamplesTable --- Key: JBEHAVE-255 URL: http://jira.codehaus.org/browse/JBEHAVE-255 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Created: (JBEHAVE-256) Stories should be retrievable from remote sources

Stories should be retrievable from remote sources - Key: JBEHAVE-256 URL: http://jira.codehaus.org/browse/JBEHAVE-256 Project: JBehave Issue Type: New Feature Components: Core

[jbehave-dev] [jira] Created: (JBEHAVE-257) Migration path from JBehave 2.x to JBehave 3.x

Migration path from JBehave 2.x to JBehave 3.x -- Key: JBEHAVE-257 URL: http://jira.codehaus.org/browse/JBEHAVE-257 Project: JBehave Issue Type: Task Components: Documentation

[jbehave-dev] [jira] Updated: (JBEHAVE-156) Allow running of multiple textual stories using a single Java RunnableStory

[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-156: - Comment: was deleted (was: This feature may or may not be relevant any more - e.g. the JBehave Web

[jbehave-dev] [jira] Assigned: (JBEHAVE-256) Stories should be retrievable from external or remote sources

[ http://jira.codehaus.org/browse/JBEHAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-256: Assignee: Mauro Talevi Stories should be retrievable from external or remote sources

[jbehave-dev] [jira] Work started: (JBEHAVE-256) Stories should be retrievable from external or remote sources

[ http://jira.codehaus.org/browse/JBEHAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-256 started by Mauro Talevi. Stories should be retrievable from external or remote sources -

[jbehave-dev] [jira] Commented: (JBEHAVE-248) Should be able to use JBehave without inheriting from a base class

[ http://jira.codehaus.org/browse/JBEHAVE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216573#action_216573 ] Mauro Talevi commented on JBEHAVE-248: -- There is now a RunnableStoryDelegator (which JUnitStory

[jbehave-dev] [jira] Assigned: (JBEHAVE-254) Review story/steps configuration

[ http://jira.codehaus.org/browse/JBEHAVE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-254: Assignee: Mauro Talevi Review story/steps configuration -

[jbehave-dev] [jira] Resolved: (JBEHAVE-255) Make column separator configurable in ExamplesTable

[ http://jira.codehaus.org/browse/JBEHAVE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-255. -- Resolution: Fixed Made table column separator configurable. Parser retrieves configuration via

[jbehave-dev] [jira] Created: (JBEHAVE-259) ClassLoader not injected by default when running stories via CLI

ClassLoader not injected by default when running stories via CLI Key: JBEHAVE-259 URL: http://jira.codehaus.org/browse/JBEHAVE-259 Project: JBehave Issue Type: Improvement

[jbehave-dev] [jira] Resolved: (JBEHAVE-259) ClassLoader not injected by default when running stories via CLI

[ http://jira.codehaus.org/browse/JBEHAVE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-259. -- Resolution: Fixed ClassLoader not injected by default when running stories via CLI

[jbehave-dev] [jira] Updated: (JBEHAVE-261) New syntax for Given with many parameters

[ http://jira.codehaus.org/browse/JBEHAVE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-261: - Fix Version/s: (was: 2.5.1) New syntax for Given with many parameters

[jbehave-dev] [jira] Commented: (JBEHAVE-258) Annotation for ParameterConverter

[ http://jira.codehaus.org/browse/JBEHAVE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216595#action_216595 ] Mauro Talevi commented on JBEHAVE-258: -- Interesting stuff, Bruno. My only comment is that the

[jbehave-dev] [jira] Created: (JBEHAVE-262) Migrate to Git for version control

Migrate to Git for version control --- Key: JBEHAVE-262 URL: http://jira.codehaus.org/browse/JBEHAVE-262 Project: JBehave Issue Type: Task Reporter: Mauro Talevi Assignee: Mauro

[jbehave-dev] [jira] Commented: (JBEHAVE-258) Annotation for ParameterConverter

[ http://jira.codehaus.org/browse/JBEHAVE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216603#action_216603 ] Mauro Talevi commented on JBEHAVE-258: -- In some cases you do need to provide parameters to the

[jbehave-dev] [jira] Commented: (JBEHAVE-261) New syntax for Given with many parameters

[ http://jira.codehaus.org/browse/JBEHAVE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216604#action_216604 ] Mauro Talevi commented on JBEHAVE-261: -- There is also the question of parsing to consider:

[jbehave-dev] [jira] Reopened: (JBEHAVE-255) Make column separator configurable in ExamplesTable

[ http://jira.codehaus.org/browse/JBEHAVE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-255: -- Need to distinguish between header and column separators. Make column separator configurable in

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-255) Make column separator configurable in ExamplesTable

[ http://jira.codehaus.org/browse/JBEHAVE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216660#action_216660 ] Mauro Talevi edited comment on JBEHAVE-255 at 4/4/10 4:47 PM: -- Need to

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-254) Review story/steps configuration

[ http://jira.codehaus.org/browse/JBEHAVE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216575#action_216575 ] Mauro Talevi edited comment on JBEHAVE-254 at 4/5/10 2:45 AM: -- Renamed

[jbehave-dev] [jira] Created: (JBEHAVE-265) Allow annotation-based configuration

Allow annotation-based configuration Key: JBEHAVE-265 URL: http://jira.codehaus.org/browse/JBEHAVE-265 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro

[jbehave-dev] [jira] Commented: (JBEHAVE-254) Review story/steps configuration

[ http://jira.codehaus.org/browse/JBEHAVE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216678#action_216678 ] Mauro Talevi commented on JBEHAVE-254: -- Created separate issue JBEHAVE-265 to track

[jbehave-dev] [jira] Resolved: (JBEHAVE-255) Make column separator configurable in ExamplesTable

[ http://jira.codehaus.org/browse/JBEHAVE-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-255. -- Resolution: Fixed ExamplesTable now accepts as distinct parameters the header and value

[jbehave-dev] [jira] Updated: (JBEHAVE-246) Improve terminology, the distinction between a story and a scenario

[ http://jira.codehaus.org/browse/JBEHAVE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-246: - Component/s: Maven Plugin Documentation Core Ant

[jbehave-dev] [jira] Created: (JBEHAVE-266) Remove deprecated method and classes from 2.x

Remove deprecated method and classes from 2.x - Key: JBEHAVE-266 URL: http://jira.codehaus.org/browse/JBEHAVE-266 Project: JBehave Issue Type: Task Reporter: Mauro Talevi

[jbehave-dev] [jira] Work started: (JBEHAVE-266) Remove deprecated method and classes from 2.x

[ http://jira.codehaus.org/browse/JBEHAVE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-266 started by Mauro Talevi. Remove deprecated method and classes from 2.x - Key: JBEHAVE-266

[jbehave-dev] [jira] Work started: (JBEHAVE-262) Migrate to Git for version control

[ http://jira.codehaus.org/browse/JBEHAVE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-262 started by Mauro Talevi. Migrate to Git for version control --- Key: JBEHAVE-262

[jbehave-dev] [jira] Commented: (JBEHAVE-262) Migrate to Git for version control

[ http://jira.codehaus.org/browse/JBEHAVE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216714#action_216714 ] Mauro Talevi commented on JBEHAVE-262: -- Configured POMs for core and web to use git. Maven

[jbehave-dev] [jira] Commented: (JBEHAVE-262) Migrate to Git for version control

[ http://jira.codehaus.org/browse/JBEHAVE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=216716#action_216716 ] Mauro Talevi commented on JBEHAVE-262: -- Also to be considered whether it makes sense to

[jbehave-dev] [jira] Created: (JBEHAVE-267) Embeddable StoryRunner should be responsible for all configurable aspects for story running

Embeddable StoryRunner should be responsible for all configurable aspects for story running --- Key: JBEHAVE-267 URL: http://jira.codehaus.org/browse/JBEHAVE-267

[jbehave-dev] [jira] Work started: (JBEHAVE-267) Embeddable StoryRunner should be responsible for all configurable aspects for story running

[ http://jira.codehaus.org/browse/JBEHAVE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-267 started by Mauro Talevi. Embeddable StoryRunner should be responsible for all configurable aspects for story running

[jbehave-dev] [jira] Assigned: (JBEHAVE-267) Embeddable StoryRunner should be responsible for all configurable aspects for story running

[ http://jira.codehaus.org/browse/JBEHAVE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-267: Assignee: Mauro Talevi Embeddable StoryRunner should be responsible for all configurable

[jbehave-dev] [jira] Updated: (JBEHAVE-248) Should be able to use JBehave without inheriting from a base class

[ http://jira.codehaus.org/browse/JBEHAVE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-248: - Comment: was deleted (was: There is now a RunnableStoryDelegator (which JUnitStory extends) that can

[jbehave-dev] [jira] Commented: (JBEHAVE-248) Should be able to use JBehave without inheriting from a base class

[ http://jira.codehaus.org/browse/JBEHAVE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=217578#action_217578 ] Mauro Talevi commented on JBEHAVE-248: -- Look at

[jbehave-dev] [jira] Updated: (JBEHAVE-267) StoryEmbedder should be responsible for all configurable aspects of story running

[ http://jira.codehaus.org/browse/JBEHAVE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-267: - Description: In 2.x, responsibilities are split between the StoryRunner and the Ant task/Maven

[jbehave-dev] [jira] Created: (JBEHAVE-273) Ensure jbehave-core dependencies are excluded or shaded

Ensure jbehave-core dependencies are excluded or shaded --- Key: JBEHAVE-273 URL: http://jira.codehaus.org/browse/JBEHAVE-273 Project: JBehave Issue Type: Task Components: Core

[jbehave-dev] [jira] Resolved: (JBEHAVE-273) Ensure jbehave-core dependencies are excluded or shaded

[ http://jira.codehaus.org/browse/JBEHAVE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-273. -- Resolution: Fixed Excluded all dependencies except paranamer, which is shaded. Ensure

[jbehave-dev] [jira] Created: (JBEHAVE-275) Ensure UTF-8 charset encoding is used consistently

Ensure UTF-8 charset encoding is used consistently -- Key: JBEHAVE-275 URL: http://jira.codehaus.org/browse/JBEHAVE-275 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Updated: (JBEHAVE-275) Ensure UTF-8 charset encoding is used consistently

[ http://jira.codehaus.org/browse/JBEHAVE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-275: - Description: In order to allow reliable and consistent support for non-English languages, a

[jbehave-dev] [jira] Updated: (JBEHAVE-276) Clarify the Scenario Reporters example and API

[ http://jira.codehaus.org/browse/JBEHAVE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-276: - Summary: Clarify the Scenario Reporters example and API (was: Clearify the Scenario Reporters

[jbehave-dev] [jira] Resolved: (JBEHAVE-274) Add example showing use of SpringJUnit4ClassRunner

[ http://jira.codehaus.org/browse/JBEHAVE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-274. -- Resolution: Fixed Add example showing use of SpringJUnit4ClassRunner

[jbehave-dev] [jira] Commented: (JBEHAVE-277) Reports are outputted to $ANT_HOME/lib instead of target dir

[ http://jira.codehaus.org/browse/JBEHAVE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=218834#action_218834 ] Mauro Talevi commented on JBEHAVE-277: -- Allowed configuration of output directory in builder to

[jbehave-dev] [jira] Commented: (JBEHAVE-279) GivenScenarios runs called scenario as PENDING not the implemented version

[ http://jira.codehaus.org/browse/JBEHAVE-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=219602#action_219602 ] Mauro Talevi commented on JBEHAVE-279: -- Warren, you need to add *all* the Steps instances

[jbehave-dev] [jira] Resolved: (JBEHAVE-278) 'And' Step (AndStep) ignores CandidateStep step

[ http://jira.codehaus.org/browse/JBEHAVE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-278. -- Resolution: Fixed 'And' Step (AndStep) ignores CandidateStep step

[jbehave-dev] [jira] Resolved: (JBEHAVE-277) Reports are outputted to $ANT_HOME/lib instead of target dir

[ http://jira.codehaus.org/browse/JBEHAVE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-277. -- Resolution: Fixed Reports are outputted to $ANT_HOME/lib instead of target dir

[jbehave-dev] [jira] Commented: (JBEHAVE-277) Reports are outputted to $ANT_HOME/lib instead of target dir

[ http://jira.codehaus.org/browse/JBEHAVE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=219610#action_219610 ] Mauro Talevi commented on JBEHAVE-277: -- The ScenarioReporterBuilder now requires explicit

[jbehave-dev] [jira] Updated: (JBEHAVE-278) 'And' Step (AndStep) ignores CandidateStep step

[ http://jira.codehaus.org/browse/JBEHAVE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-278: - Fix Version/s: 3.0 'And' Step (AndStep) ignores CandidateStep step

[jbehave-dev] [jira] Created: (JBEHAVE-280) Review MostUsefulStoryConfiguration defaults

Review MostUsefulStoryConfiguration defaults Key: JBEHAVE-280 URL: http://jira.codehaus.org/browse/JBEHAVE-280 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Created: (JBEHAVE-281) Multiple And steps are not matched

Multiple And steps are not matched -- Key: JBEHAVE-281 URL: http://jira.codehaus.org/browse/JBEHAVE-281 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 2.5.2

[jbehave-dev] [jira] Resolved: (JBEHAVE-281) Multiple And steps are not matched

[ http://jira.codehaus.org/browse/JBEHAVE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-281. -- Resolution: Fixed Multiple And steps are not matched --

[jbehave-dev] [jira] Updated: (JBEHAVE-281) Multiple And steps are not matched

[ http://jira.codehaus.org/browse/JBEHAVE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-281: - Fix Version/s: 3.0 Multiple And steps are not matched --

[jbehave-dev] [jira] Updated: (JBEHAVE-282) Using GivenScenarios causes failed tests to be forgotten

[ http://jira.codehaus.org/browse/JBEHAVE-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-282: - Fix Version/s: 3.0 Using GivenScenarios causes failed tests to be forgotten

[jbehave-dev] [jira] Created: (JBEHAVE-283) Report Renderer should be failure aware

Report Renderer should be failure aware --- Key: JBEHAVE-283 URL: http://jira.codehaus.org/browse/JBEHAVE-283 Project: JBehave Issue Type: Improvement Components: Ant extension, Core, Maven

[jbehave-dev] [jira] Created: (JBEHAVE-284) Allow story embedder to render reports

Allow story embedder to render reports -- Key: JBEHAVE-284 URL: http://jira.codehaus.org/browse/JBEHAVE-284 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro

[jbehave-dev] [jira] Created: (JBEHAVE-285) Add stepdocs documentation page

Add stepdocs documentation page --- Key: JBEHAVE-285 URL: http://jira.codehaus.org/browse/JBEHAVE-285 Project: JBehave Issue Type: Task Components: Documentation Reporter: Mauro Talevi

[jbehave-dev] [jira] Updated: (JBEHAVE-283) Report Renderer should be failure aware

[ http://jira.codehaus.org/browse/JBEHAVE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-283: - Description: If a user wants to run through all scenarios/stories and generate a collective view of

[jbehave-dev] [jira] Resolved: (JBEHAVE-285) Add stepdocs documentation page

[ http://jira.codehaus.org/browse/JBEHAVE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-285. -- Resolution: Fixed Add stepdocs documentation page ---

[jbehave-dev] [jira] Resolved: (JBEHAVE-283) Report Renderer should be failure aware

[ http://jira.codehaus.org/browse/JBEHAVE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-283. -- Resolution: Fixed Report Renderer should be failure aware ---

[jbehave-dev] [jira] Updated: (JBEHAVE-283) Report Renderer should be failure aware

[ http://jira.codehaus.org/browse/JBEHAVE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-283: - Fix Version/s: (was: 2.5.5) 3.0 Report Renderer should be failure aware

[jbehave-dev] [jira] Updated: (JBEHAVE-285) Add stepdocs documentation page

[ http://jira.codehaus.org/browse/JBEHAVE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-285: - Fix Version/s: (was: 2.5.5) 3.0 Add stepdocs documentation page

[jbehave-dev] [jira] Updated: (JBEHAVE-285) Add stepdocs documentation page

[ http://jira.codehaus.org/browse/JBEHAVE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-285: - Fix Version/s: 2.5.5 Add stepdocs documentation page ---

[jbehave-dev] [jira] Work started: (JBEHAVE-284) Allow story embedder to render reports

[ http://jira.codehaus.org/browse/JBEHAVE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-284 started by Mauro Talevi. Allow story embedder to render reports -- Key: JBEHAVE-284

[jbehave-dev] [jira] Updated: (JBEHAVE-280) Review MostUsefulStoryConfiguration defaults

[ http://jira.codehaus.org/browse/JBEHAVE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-280: - Description: Review and update defaults so as to minimise configuration. Following defaults have

[jbehave-dev] [jira] Work started: (JBEHAVE-280) Review MostUsefulStoryConfiguration defaults

[ http://jira.codehaus.org/browse/JBEHAVE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-280 started by Mauro Talevi. Review MostUsefulStoryConfiguration defaults Key: JBEHAVE-280

[jbehave-dev] [jira] Assigned: (JBEHAVE-284) Allow story embedder to render reports

[ http://jira.codehaus.org/browse/JBEHAVE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-284: Assignee: Mauro Talevi Allow story embedder to render reports

[jbehave-dev] [jira] Created: (JBEHAVE-286) Adopt builder syntax for Story/StepsConfiguration

Adopt builder syntax for Story/StepsConfiguration -- Key: JBEHAVE-286 URL: http://jira.codehaus.org/browse/JBEHAVE-286 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Assigned: (JBEHAVE-286) Adopt builder syntax for Story/StepsConfiguration

[ http://jira.codehaus.org/browse/JBEHAVE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-286: Assignee: Mauro Talevi Adopt builder syntax for Story/StepsConfiguration

[jbehave-dev] [jira] Updated: (JBEHAVE-284) Allow story embedder to render reports

[ http://jira.codehaus.org/browse/JBEHAVE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-284: - Description: If report rendering were the concern of the story embedder, it would allow the

[jbehave-dev] [jira] Resolved: (JBEHAVE-267) StoryEmbedder should be responsible for all configurable aspects of story running

[ http://jira.codehaus.org/browse/JBEHAVE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-267. -- Resolution: Fixed StoryEmbedder should be responsible for all configurable aspects of story

[jbehave-dev] [jira] Resolved: (JBEHAVE-266) Remove deprecated method and classes from 2.x

[ http://jira.codehaus.org/browse/JBEHAVE-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-266. -- Resolution: Fixed Remove deprecated method and classes from 2.x

[jbehave-dev] [jira] Resolved: (JBEHAVE-280) Review MostUsefulStoryConfiguration defaults

[ http://jira.codehaus.org/browse/JBEHAVE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-280. -- Resolution: Fixed Review MostUsefulStoryConfiguration defaults

<    1   2   3   4   5   6   7   8   9   10   >