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

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

[ http://jira.codehaus.org/browse/JBEHAVE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220572#action_220572 ] Mauro Talevi commented on JBEHAVE-284: -- Added renderReportsAfterStories=[true|false] flag (defa

[jbehave-dev] [jira] Resolved: (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 resolved JBEHAVE-284. -- Resolution: Fixed > Allow story embedder to render reports > --

[jbehave-dev] [jira] Resolved: (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 resolved JBEHAVE-286. -- Resolution: Fixed > Adopt builder syntax for Story/StepsConfiguration > ---

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

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

[jbehave-dev] [jira] Resolved: (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 resolved JBEHAVE-248. -- Resolution: Fixed > Should be able to use JBehave without inheriting from a base class > ---

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

[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-156: - Description: In order to avoid the need to define a Java class for each textual story As a story

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

[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-156. -- Resolution: Fixed Now that StoryEmbedder is responsible for story running, we can have multiple ent

[jbehave-dev] [jira] Updated: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder

[ http://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-207: - Fix Version/s: 2.5.6 > Exclude SCM patterns from ScenarioClassNameFinder > ---

[jbehave-dev] [jira] Updated: (JBEHAVE-287) Dry-run Scenario to determine that no steps are Pending

[ http://jira.codehaus.org/browse/JBEHAVE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-287: - Fix Version/s: 2.5.6 > Dry-run Scenario to determine that no steps are Pending > -

[jbehave-dev] [jira] Assigned: (JBEHAVE-287) Dry-run Scenario to determine that no steps are Pending

[ http://jira.codehaus.org/browse/JBEHAVE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-287: Assignee: Mauro Talevi > Dry-run Scenario to determine that no steps are Pending > -

[jbehave-dev] [jira] Resolved: (JBEHAVE-287) Dry-run Scenario to determine that no steps are Pending

[ http://jira.codehaus.org/browse/JBEHAVE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-287. -- Resolution: Fixed Added StepsConfiguration.doDryRun(boolean) method to control dry run mode. > Dr

[jbehave-dev] [jira] Updated: (JBEHAVE-287) Dry-run Scenario to determine that no steps are Pending

[ http://jira.codehaus.org/browse/JBEHAVE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-287: - Fix Version/s: 3.0 > Dry-run Scenario to determine that no steps are Pending > ---

[jbehave-dev] [jira] Resolved: (JBEHAVE-207) Exclude SCM patterns from ScenarioClassNameFinder

[ http://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-207. -- Resolution: Won't Fix Thanks for clarification. This seems to confirm that the issue is with the e

[jbehave-dev] [jira] Created: (JBEHAVE-288) Replace Ensure methods with Hamcrest direct invocations

Replace Ensure methods with Hamcrest direct invocations --- Key: JBEHAVE-288 URL: http://jira.codehaus.org/browse/JBEHAVE-288 Project: JBehave Issue Type: Task Components: Core

[jbehave-dev] [jira] Resolved: (JBEHAVE-288) Replace Ensure methods with Hamcrest direct invocations

[ http://jira.codehaus.org/browse/JBEHAVE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-288. -- Resolution: Fixed Assignee: Mauro Talevi > Replace Ensure methods with Hamcrest direct invocat

[jbehave-dev] [jira] Created: (JBEHAVE-289) Moved configuration and runner classes to separate packages

Moved configuration and runner classes to separate packages --- Key: JBEHAVE-289 URL: http://jira.codehaus.org/browse/JBEHAVE-289 Project: JBehave Issue Type: Improvement Comp

[jbehave-dev] [jira] Commented: (JBEHAVE-288) Replace Ensure methods with Hamcrest direct invocations

[ http://jira.codehaus.org/browse/JBEHAVE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221693#action_221693 ] Mauro Talevi commented on JBEHAVE-288: -- Precisely my point. One should be able to use any asse

[jbehave-dev] [jira] Created: (JBEHAVE-291) Add method and steps instance information to matching events in StepsMonitor

Add method and steps instance information to matching events in StepsMonitor Key: JBEHAVE-291 URL: http://jira.codehaus.org/browse/JBEHAVE-291 Project: JBehave Issu

[jbehave-dev] [jira] Updated: (JBEHAVE-290) Stack Overflow when parsing a scenario with a very long step

[ http://jira.codehaus.org/browse/JBEHAVE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-290: - Component/s: Core Fix Version/s: 3.0 2.5.7 Assignee: Mauro Talevi >

[jbehave-dev] [jira] Resolved: (JBEHAVE-291) Add method and steps instance information to matching events in StepsMonitor

[ http://jira.codehaus.org/browse/JBEHAVE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-291. -- Resolution: Fixed Assignee: Mauro Talevi > Add method and steps instance information to matchi

[jbehave-dev] [jira] Resolved: (JBEHAVE-290) Stack Overflow when parsing a scenario with a very long step

[ http://jira.codehaus.org/browse/JBEHAVE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-290. -- Resolution: Fixed > Stack Overflow when parsing a scenario with a very long step > -

[jbehave-dev] [jira] Commented: (JBEHAVE-290) Stack Overflow when parsing a scenario with a very long step

[ http://jira.codehaus.org/browse/JBEHAVE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222029#action_222029 ] Mauro Talevi commented on JBEHAVE-290: -- Thanks for the patch. Applied, tested and released in

[jbehave-dev] [jira] Updated: (JBEHAVE-220) Allow per-scenario meta-information

[ http://jira.codehaus.org/browse/JBEHAVE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-220: - Fix Version/s: 3.0 > Allow per-scenario meta-information > --- > >

[jbehave-dev] [jira] Created: (JBEHAVE-293) Move I/O related components into separate package from parsing components

Move I/O related components into separate package from parsing components - Key: JBEHAVE-293 URL: http://jira.codehaus.org/browse/JBEHAVE-293 Project: JBehave Issue Type

[jbehave-dev] [jira] Created: (JBEHAVE-294) Refactor step pattern parsing to allow non-regex implementations

Refactor step pattern parsing to allow non-regex implementations - Key: JBEHAVE-294 URL: http://jira.codehaus.org/browse/JBEHAVE-294 Project: JBehave Issue Type: Improvement

[jbehave-dev] [jira] Work started: (JBEHAVE-294) Separate step pattern parsing from the matching

[ http://jira.codehaus.org/browse/JBEHAVE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-294 started by Mauro Talevi. > Separate step pattern parsing from the matching > > > Key: JBE

[jbehave-dev] [jira] Assigned: (JBEHAVE-294) Separate step pattern parsing from the matching

[ http://jira.codehaus.org/browse/JBEHAVE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-294: Assignee: Mauro Talevi > Separate step pattern parsing from the matching >

[jbehave-dev] [jira] Updated: (JBEHAVE-294) Separate step pattern parsing from the matching

[ http://jira.codehaus.org/browse/JBEHAVE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-294: - Summary: Separate step pattern parsing from the matching (was: Refactor step pattern parsing to allo

[jbehave-dev] [jira] Resolved: (JBEHAVE-293) Move I/O related components into separate package from parsing components

[ http://jira.codehaus.org/browse/JBEHAVE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-293. -- Resolution: Fixed > Move I/O related components into separate package from parsing components >

[jbehave-dev] [jira] Resolved: (JBEHAVE-289) Moved configuration and runner classes to separate packages

[ http://jira.codehaus.org/browse/JBEHAVE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-289. -- Resolution: Fixed > Moved configuration and runner classes to separate packages > --

[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-tabpanel&focusedCommentId=01#action_01 ] Mauro Talevi commented on JBEHAVE-262: -- Re-cloned trunk only and only split core, web and site

[jbehave-dev] [jira] Resolved: (JBEHAVE-294) Separate step pattern parsing from the matching

[ http://jira.codehaus.org/browse/JBEHAVE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-294. -- Resolution: Fixed > Separate step pattern parsing from the matching > -

[jbehave-dev] [jira] Resolved: (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 resolved JBEHAVE-256. -- Resolution: Fixed > Stories should be retrievable from external or remote sources >

[jbehave-dev] [jira] Created: (JBEHAVE-295) Allow non-HTML file reports to be rendered undecorated with syntax highlighter

Allow non-HTML file reports to be rendered undecorated with syntax highlighter -- Key: JBEHAVE-295 URL: http://jira.codehaus.org/browse/JBEHAVE-295 Project: JBehave

[jbehave-dev] [jira] Resolved: (JBEHAVE-295) Allow non-HTML file reports to be rendered undecorated with syntax highlighter

[ http://jira.codehaus.org/browse/JBEHAVE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-295. -- Resolution: Fixed Set property "decorateNonHtml"="false" in StoryReporterBuilder.useRenderingProper

[jbehave-dev] [jira] Commented: (JBEHAVE-292) Failed To Instantiate Scenario - ClassNotFoundException

[ http://jira.codehaus.org/browse/JBEHAVE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68#action_68 ] Mauro Talevi commented on JBEHAVE-292: -- Tom, your problem seems to be a classpath one. I could

[jbehave-dev] [jira] Commented: (JBEHAVE-292) Failed To Instantiate Scenario - ClassNotFoundException

[ http://jira.codehaus.org/browse/JBEHAVE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222425#action_222425 ] Mauro Talevi commented on JBEHAVE-292: -- Your updated project works fine for me (Mac JDK 1.6).

[jbehave-dev] [jira] Commented: (JBEHAVE-292) Failed To Instantiate Scenario - ClassNotFoundException

[ http://jira.codehaus.org/browse/JBEHAVE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=222555#action_222555 ] Mauro Talevi commented on JBEHAVE-292: -- I've verified that LoginProject works on Windows (XP) t

[jbehave-dev] [jira] Resolved: (JBEHAVE-292) Failed To Instantiate Scenario - ClassNotFoundException

[ http://jira.codehaus.org/browse/JBEHAVE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-292. -- Resolution: Not A Bug No problem, Tom. Glad we could help to sort out the issue. > Failed To Insta

[jbehave-dev] [jira] Created: (JBEHAVE-296) Failure exception being thrown in PrintStream reporters prevents the delegating reporter from completing

Failure exception being thrown in PrintStream reporters prevents the delegating reporter from completing Key: JBEHAVE-296 URL: http://jira.codehaus.org/browse

[jbehave-dev] [jira] Resolved: (JBEHAVE-296) Failure exception being thrown in PrintStream reporters prevents the delegating reporter from completing

[ http://jira.codehaus.org/browse/JBEHAVE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-296. -- Resolution: Fixed > Failure exception being thrown in PrintStream reporters prevents the > delegati

[jbehave-dev] [jira] Updated: (JBEHAVE-296) Step failure exception being thrown in PrintStream reporters prevents the delegating reporter from completing

[ http://jira.codehaus.org/browse/JBEHAVE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-296: - Description: PrintStream reporters should not throw any exception upon step failures, since they prev

[jbehave-dev] [jira] Created: (JBEHAVE-297) GivenScenarios comma-separated paths should support newlines between paths

GivenScenarios comma-separated paths should support newlines between paths -- Key: JBEHAVE-297 URL: http://jira.codehaus.org/browse/JBEHAVE-297 Project: JBehave Issue Ty

[jbehave-dev] [jira] Updated: (JBEHAVE-297) GivenScenarios comma-separated paths should support newlines between paths

[ http://jira.codehaus.org/browse/JBEHAVE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-297: - Fix Version/s: 3.0 > GivenScenarios comma-separated paths should support newlines between paths >

[jbehave-dev] [jira] Resolved: (JBEHAVE-297) GivenScenarios comma-separated paths should support newlines between paths

[ http://jira.codehaus.org/browse/JBEHAVE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-297. -- Resolution: Fixed > GivenScenarios comma-separated paths should support newlines between paths > ---

[jbehave-dev] [jira] Created: (JBEHAVE-298) CandidateStep finder

CandidateStep finder Key: JBEHAVE-298 URL: http://jira.codehaus.org/browse/JBEHAVE-298 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix For: 3.0 In

[jbehave-dev] [jira] Commented: (JBEHAVE-299) Problems with jBehave, Maven and Windows

[ http://jira.codehaus.org/browse/JBEHAVE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224147#action_224147 ] Mauro Talevi commented on JBEHAVE-299: -- The scenario textual files are not being copied to the

[jbehave-dev] [jira] Created: (JBEHAVE-300) Rename StepResult methods for consistency and clarity

Rename StepResult methods for consistency and clarity - Key: JBEHAVE-300 URL: http://jira.codehaus.org/browse/JBEHAVE-300 Project: JBehave Issue Type: Improvement Reporter: Maur

[jbehave-dev] [jira] Created: (JBEHAVE-301) Rename embeddedStory flag to givenStory in StoryRunner

Rename embeddedStory flag to givenStory in StoryRunner -- Key: JBEHAVE-301 URL: http://jira.codehaus.org/browse/JBEHAVE-301 Project: JBehave Issue Type: Improvement Components: Co

[jbehave-dev] [jira] Created: (JBEHAVE-302) Rename StepCreator to StepCollector

Rename StepCreator to StepCollector --- Key: JBEHAVE-302 URL: http://jira.codehaus.org/browse/JBEHAVE-302 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi

[jbehave-dev] [jira] Updated: (JBEHAVE-302) Separate step matching from step creation in CandidateStep

[ http://jira.codehaus.org/browse/JBEHAVE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-302: - Description: CandidateStep is becoming too big and would benefit from a separation of concern between

[jbehave-dev] [jira] Work started: (JBEHAVE-302) Separate step matching from step creation in CandidateStep

[ http://jira.codehaus.org/browse/JBEHAVE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-302 started by Mauro Talevi. > Separate step matching from step creation in CandidateStep > -- > >

[jbehave-dev] [jira] Updated: (JBEHAVE-302) Separate step matching from step creation in CandidateStep

[ http://jira.codehaus.org/browse/JBEHAVE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-302: - Description: CandidateStep is becoming too big and would benefit from a separation of concern between

[jbehave-dev] [jira] Resolved: (JBEHAVE-301) Rename embeddedStory flag to givenStory in StoryRunner

[ http://jira.codehaus.org/browse/JBEHAVE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-301. -- Resolution: Fixed > Rename embeddedStory flag to givenStory in StoryRunner > ---

[jbehave-dev] [jira] Resolved: (JBEHAVE-302) Separate step matching from step creation in CandidateStep

[ http://jira.codehaus.org/browse/JBEHAVE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-302. -- Resolution: Fixed > Separate step matching from step creation in CandidateStep > ---

[jbehave-dev] [jira] Created: (JBEHAVE-303) Mark start/end of all parameter values in step creation

Mark start/end of all parameter values in step creation --- Key: JBEHAVE-303 URL: http://jira.codehaus.org/browse/JBEHAVE-303 Project: JBehave Issue Type: Improvement Components:

[jbehave-dev] [jira] Created: (JBEHAVE-304) Better rendering of ExamplesTable as parameter in HTML

Better rendering of ExamplesTable as parameter in HTML -- Key: JBEHAVE-304 URL: http://jira.codehaus.org/browse/JBEHAVE-304 Project: JBehave Issue Type: Improvement Components: Co

[jbehave-dev] [jira] Created: (JBEHAVE-305) Improve reporting of failure

Improve reporting of failure Key: JBEHAVE-305 URL: http://jira.codehaus.org/browse/JBEHAVE-305 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi As

[jbehave-dev] [jira] Updated: (JBEHAVE-304) Better rendering of ExamplesTable as parameter in HTML

[ http://jira.codehaus.org/browse/JBEHAVE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-304: - Description: When outputting example tables as parameters in HTML the newlines between rows are ignor

[jbehave-dev] [jira] Work started: (JBEHAVE-305) Improve reporting of failure

[ http://jira.codehaus.org/browse/JBEHAVE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-305 started by Mauro Talevi. > Improve reporting of failure > > > Key: JBEHAVE-305 > URL: http://j

[jbehave-dev] [jira] Work started: (JBEHAVE-304) Better rendering of ExamplesTable as parameter in HTML

[ http://jira.codehaus.org/browse/JBEHAVE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-304 started by Mauro Talevi. > Better rendering of ExamplesTable as parameter in HTML > -- > >

[jbehave-dev] [jira] Created: (JBEHAVE-306) StoryReporterBuilder method names should be more consistent

StoryReporterBuilder method names should be more consistent --- Key: JBEHAVE-306 URL: http://jira.codehaus.org/browse/JBEHAVE-306 Project: JBehave Issue Type: Improvement Comp

[jbehave-dev] [jira] Resolved: (JBEHAVE-306) StoryReporterBuilder method names should be more consistent

[ http://jira.codehaus.org/browse/JBEHAVE-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-306. -- Resolution: Fixed > StoryReporterBuilder method names should be more consistent > --

[jbehave-dev] [jira] Updated: (JBEHAVE-305) Improve reporting of failure

[ http://jira.codehaus.org/browse/JBEHAVE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-305: - Description: PrintStreamStoryReporter and subclasses have the reportErrors flag that prints the failu

[jbehave-dev] [jira] Created: (JBEHAVE-307) Remove redundant getter methods in RunnableStory

Remove redundant getter methods in RunnableStory Key: JBEHAVE-307 URL: http://jira.codehaus.org/browse/JBEHAVE-307 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Resolved: (JBEHAVE-307) Remove redundant getter methods in RunnableStory

[ http://jira.codehaus.org/browse/JBEHAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-307. -- Resolution: Fixed > Remove redundant getter methods in RunnableStory > -

[jbehave-dev] [jira] Updated: (JBEHAVE-267) Embedder 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 plugin

[jbehave-dev] [jira] Created: (JBEHAVE-308) Move configuration of stepdocs from StoryConfiguration to Embedder

Move configuration of stepdocs from StoryConfiguration to Embedder -- Key: JBEHAVE-308 URL: http://jira.codehaus.org/browse/JBEHAVE-308 Project: JBehave Issue Type: Improvement

[jbehave-dev] [jira] Resolved: (JBEHAVE-308) Move configuration of stepdocs from StoryConfiguration to Embedder

[ http://jira.codehaus.org/browse/JBEHAVE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-308. -- Resolution: Fixed > Move configuration of stepdocs from StoryConfiguration to Embedder > ---

[jbehave-dev] [jira] Reopened: (JBEHAVE-308) Move configuration of stepdocs from StoryConfiguration to Embedder

[ http://jira.codehaus.org/browse/JBEHAVE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-308: -- > Move configuration of stepdocs from StoryConfiguration to Embedder > -

[jbehave-dev] [jira] Updated: (JBEHAVE-308) Make configuration elements coordinated

[ http://jira.codehaus.org/browse/JBEHAVE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-308: - Description: A better coordination of different configuration objects (for story, steps and embedder)

[jbehave-dev] [jira] Created: (JBEHAVE-310) Rename failure handling strategies and implement as standalone classes

Rename failure handling strategies and implement as standalone classes -- Key: JBEHAVE-310 URL: http://jira.codehaus.org/browse/JBEHAVE-310 Project: JBehave Issue Type: Impr

[jbehave-dev] [jira] Resolved: (JBEHAVE-310) Rename failure handling strategies and implement as standalone classes

[ http://jira.codehaus.org/browse/JBEHAVE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-310. -- Resolution: Fixed Fix Version/s: 3.0 > Rename failure handling strategies and implement as st

[jbehave-dev] [jira] Updated: (JBEHAVE-308) Consolidate configuration objects

[ http://jira.codehaus.org/browse/JBEHAVE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-308: - Description: Merge story and steps configurations into single Configuration object, that now use the

[jbehave-dev] [jira] Resolved: (JBEHAVE-308) Consolidate configuration objects

[ http://jira.codehaus.org/browse/JBEHAVE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-308. -- Resolution: Fixed > Consolidate configuration objects > - > >

[jbehave-dev] [jira] Resolved: (JBEHAVE-303) Mark start/end of all parameter values in step creation

[ http://jira.codehaus.org/browse/JBEHAVE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-303. -- Resolution: Fixed > Mark start/end of all parameter values in step creation > --

[jbehave-dev] [jira] Updated: (JBEHAVE-304) Fix rendering of newlines in ExamplesTable as parameter in HTML

[ http://jira.codehaus.org/browse/JBEHAVE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-304: - Description: When outputting example tables as parameters in HTML the newlines between rows are ignor

[jbehave-dev] [jira] Resolved: (JBEHAVE-300) Rename StepResult methods for consistency and clarity

[ http://jira.codehaus.org/browse/JBEHAVE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-300. -- Resolution: Fixed > Rename StepResult methods for consistency and clarity >

[jbehave-dev] [jira] Resolved: (JBEHAVE-304) Fix rendering of newlines in ExamplesTable as parameter in HTML

[ http://jira.codehaus.org/browse/JBEHAVE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-304. -- Resolution: Fixed > Fix rendering of newlines in ExamplesTable as parameter in HTML > --

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

[ http://jira.codehaus.org/browse/JBEHAVE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-262. -- Resolution: Fixed > Migrate to Git for version control > --- > >

[jbehave-dev] [jira] Reopened: (JBEHAVE-307) Remove redundant getter methods in RunnableStory

[ http://jira.codehaus.org/browse/JBEHAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-307: -- > Remove redundant getter methods in RunnableStory > >

[jbehave-dev] [jira] Commented: (JBEHAVE-307) Remove redundant getter methods in RunnableStory

[ http://jira.codehaus.org/browse/JBEHAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225159#action_225159 ] Mauro Talevi commented on JBEHAVE-307: -- Added protected methods configuration() and candidateSt

[jbehave-dev] [jira] Resolved: (JBEHAVE-305) Improve reporting of failure

[ http://jira.codehaus.org/browse/JBEHAVE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-305. -- Resolution: Fixed > Improve reporting of failure > > >

[jbehave-dev] [jira] Updated: (JBEHAVE-309) default report location determined by location of jbehave jar

[ http://jira.codehaus.org/browse/JBEHAVE-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-309: - Fix Version/s: 3.0 > default report location determined by location of jbehave jar > -

[jbehave-dev] [jira] Created: (JBEHAVE-311) Pull up StepRunner and StepResult interfaces

Pull up StepRunner and StepResult interfaces Key: JBEHAVE-311 URL: http://jira.codehaus.org/browse/JBEHAVE-311 Project: JBehave Issue Type: Improvement Components: Core Repor

[jbehave-dev] [jira] Updated: (JBEHAVE-311) Allow StepRunner implementations to be overridable in Steps

[ http://jira.codehaus.org/browse/JBEHAVE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-311: - Description: Pull up StepRunner and StepResult interface from Steps, make the StepRunner implementati

[jbehave-dev] [jira] Updated: (JBEHAVE-311) Move step creation concern from Steps to StepCreator

[ http://jira.codehaus.org/browse/JBEHAVE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-311: - Description: Move step creation concern from Steps to StepCreator Refactor CandidateSteps interface m

[jbehave-dev] [jira] Created: (JBEHAVE-313) Change terminology of report rendering to view generation

Change terminology of report rendering to view generation - Key: JBEHAVE-313 URL: http://jira.codehaus.org/browse/JBEHAVE-313 Project: JBehave Issue Type: Improvement Componen

[jbehave-dev] [jira] Updated: (JBEHAVE-313) Change terminology of report rendering to view generation

[ http://jira.codehaus.org/browse/JBEHAVE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-313: - Description: To avoid confusion, change terminology reporting rendering to stories view generation. T

[jbehave-dev] [jira] Resolved: (JBEHAVE-313) Change terminology of report rendering to view generation

[ http://jira.codehaus.org/browse/JBEHAVE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-313. -- Resolution: Fixed > Change terminology of report rendering to view generation >

[jbehave-dev] [jira] Assigned: (JBEHAVE-313) Change terminology of report rendering to view generation

[ http://jira.codehaus.org/browse/JBEHAVE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-313: Assignee: Mauro Talevi > Change terminology of report rendering to view generation > ---

[jbehave-dev] [jira] Resolved: (JBEHAVE-298) CandidateStep finder

[ http://jira.codehaus.org/browse/JBEHAVE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-298. -- Resolution: Fixed > CandidateStep finder > > > Key: JBEHAVE-298

[jbehave-dev] [jira] Assigned: (JBEHAVE-298) CandidateStep finder

[ http://jira.codehaus.org/browse/JBEHAVE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-298: Assignee: Mauro Talevi > CandidateStep finder > > > Key: JB

[jbehave-dev] [jira] Resolved: (JBEHAVE-311) Move step creation concern from Steps to StepCreator

[ http://jira.codehaus.org/browse/JBEHAVE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-311. -- Resolution: Fixed > Move step creation concern from Steps to StepCreator > -

[jbehave-dev] [jira] Updated: (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 updated JBEHAVE-274: - Component/s: Documentation Description: A SpringJUnit4ScenarioRunner example to show how the r

[jbehave-dev] [jira] Updated: (JBEHAVE-263) Allow lazy parameter convertion

[ http://jira.codehaus.org/browse/JBEHAVE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-263: - Component/s: Core Description: Right now the converters are called before running the scenario

[jbehave-dev] [jira] Updated: (JBEHAVE-314) Use "parameter" language in place of "arg" in StepMonitor and StepCreator

[ http://jira.codehaus.org/browse/JBEHAVE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-314: - Summary: Use "parameter" language in place of "arg" in StepMonitor and StepCreator (was: Rename StepM

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