[jbehave-dev] [jira] Commented: (JBEHAVE-205) Is there a way to sync scenerios with classes?

[ http://jira.codehaus.org/browse/JBEHAVE-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=197714#action_197714 ] Mauro Talevi commented on JBEHAVE-205: -- At the moment, the process of keeping in sync the

[jbehave-dev] [jira] Created: (JBEHAVE-206) Regex overflow in using Examples table

Regex overflow in using Examples table -- Key: JBEHAVE-206 URL: http://jira.codehaus.org/browse/JBEHAVE-206 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 2.3.2, 2.3.1,

[jbehave-dev] [jira] Commented: (JBEHAVE-206) Regex overflow in using Examples table

[ http://jira.codehaus.org/browse/JBEHAVE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=197799#action_197799 ] Mauro Talevi commented on JBEHAVE-206: -- One quick workaround could be to support reading

[jbehave-dev] [jira] Commented: (JBEHAVE-161) HTML-based scenario reporter

[ http://jira.codehaus.org/browse/JBEHAVE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=197801#action_197801 ] Mauro Talevi commented on JBEHAVE-161: -- Thanks Mirko. We'll take a look at these in the next

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

Exclude SCM patterns from ScenarioClassNameFinder - Key: JBEHAVE-207 URL: http://jira.codehaus.org/browse/JBEHAVE-207 Project: JBehave Issue Type: Improvement Reporter: Mauro

[jbehave-dev] [jira] Work started: (JBEHAVE-161) HTML-based scenario reporter

[ http://jira.codehaus.org/browse/JBEHAVE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-161 started by Mauro Talevi. HTML-based scenario reporter Key: JBEHAVE-161 URL:

[jbehave-dev] [jira] Assigned: (JBEHAVE-161) HTML-based scenario reporter

[ http://jira.codehaus.org/browse/JBEHAVE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-161: Assignee: Mauro Talevi HTML-based scenario reporter

[jbehave-dev] [jira] Updated: (JBEHAVE-210) Report embedded status in before/after story events

[ http://jira.codehaus.org/browse/JBEHAVE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-210: - Affects Version/s: 2.3 2.3.1 2.3.2 Report embedded

[jbehave-dev] [jira] Updated: (JBEHAVE-211) StringListConverter converts an empty String to a one element List instead of an empty List

[ http://jira.codehaus.org/browse/JBEHAVE-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-211: - Fix Version/s: 2.4 Assignee: Mauro Talevi Thanks Cyril. I'll apply patch and release it in

[jbehave-dev] [jira] Reopened: (JBEHAVE-195) Incorrect uploaded filename on Windows IE

[ http://jira.codehaus.org/browse/JBEHAVE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-195: -- Assignee: Mauro Talevi Using new File(path).getName() to extract the file name (without parent

[jbehave-dev] [jira] Resolved: (JBEHAVE-195) Incorrect uploaded filename on Windows IE

[ http://jira.codehaus.org/browse/JBEHAVE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-195. -- Resolution: Fixed Incorrect uploaded filename on Windows IE

[jbehave-dev] [jira] Created: (JBEHAVE-212) Starting words are not updated when keywords are overridden in steps configuration

Starting words are not updated when keywords are overridden in steps configuration -- Key: JBEHAVE-212 URL: http://jira.codehaus.org/browse/JBEHAVE-212 Project: JBehave

[jbehave-dev] [jira] Resolved: (JBEHAVE-212) Starting words are not updated when keywords are overridden in steps configuration

[ http://jira.codehaus.org/browse/JBEHAVE-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-212. -- Resolution: Fixed Applied patch by Cristiano Gavião. Added test to verify behaviour. Starting

[jbehave-dev] [jira] Created: (JBEHAVE-213) Scenario runner form submission should support both GET And POST methods

Scenario runner form submission should support both GET And POST methods -- Key: JBEHAVE-213 URL: http://jira.codehaus.org/browse/JBEHAVE-213 Project: JBehave Issue

[jbehave-dev] [jira] Updated: (JBEHAVE-213) Scenario runner form submission should support both GET and POST methods

[ http://jira.codehaus.org/browse/JBEHAVE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-213: - Description: POST is required for very long scenarios - and it now the default. To change invoke

[jbehave-dev] [jira] Updated: (JBEHAVE-213) Scenario runner form submission should support both GET And POST methods

[ http://jira.codehaus.org/browse/JBEHAVE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-213: - Fix Version/s: web-2.1.6 Scenario runner form submission should support both GET And POST methods

[jbehave-dev] [jira] Resolved: (JBEHAVE-214) Allow for multiple aliases for a given step

[ http://jira.codehaus.org/browse/JBEHAVE-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-214. -- Resolution: Duplicate Implemented in JBEHAVE-131. Allow for multiple aliases for a given step

[jbehave-dev] [jira] Updated: (JBEHAVE-213) Scenario runner form submission should support both GET and POST methods

[ http://jira.codehaus.org/browse/JBEHAVE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-213: - Description: POST is required for executing very long scenarios - and is now the default. Can be

[jbehave-dev] [jira] Resolved: (JBEHAVE-213) Scenario runner form submission should support both GET and POST methods

[ http://jira.codehaus.org/browse/JBEHAVE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-213. -- Resolution: Fixed Scenario runner form submission should support both GET and POST methods

[jbehave-dev] [jira] Updated: (JBEHAVE-213) Scenario runner form submission should support both GET and POST methods

[ http://jira.codehaus.org/browse/JBEHAVE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-213: - Description: POST is required for very long scenarios - and it now the default. Can be changed via

[jbehave-dev] [jira] Updated: (JBEHAVE-217) Allow configuration to be overridden

[ http://jira.codehaus.org/browse/JBEHAVE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-217: - Fix Version/s: 2.4 Assignee: Mauro Talevi Summary: Allow configuration to be

[jbehave-dev] [jira] Resolved: (JBEHAVE-217) Allow configuration to be overridden

[ http://jira.codehaus.org/browse/JBEHAVE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-217. -- Resolution: Fixed Added useConfiguration(Configuration) method to Scenario to override existing or

[jbehave-dev] [jira] Commented: (JBEHAVE-218) Standardize and make file/directory layout configurable

[ http://jira.codehaus.org/browse/JBEHAVE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202230#action_202230 ] Mauro Talevi commented on JBEHAVE-218: -- Scenarios can live both in Maven main or test

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

[ http://jira.codehaus.org/browse/JBEHAVE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202234#action_202234 ] Mauro Talevi commented on JBEHAVE-220: -- At the moment, you could put meta-info in the scenario

[jbehave-dev] [jira] Created: (JBEHAVE-222) Add/rename examples events in ScenarioReporter

Add/rename examples events in ScenarioReporter --- Key: JBEHAVE-222 URL: http://jira.codehaus.org/browse/JBEHAVE-222 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Resolved: (JBEHAVE-222) Add/rename examples events in ScenarioReporter

[ http://jira.codehaus.org/browse/JBEHAVE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-222. -- Resolution: Fixed Add/rename examples events in ScenarioReporter

[jbehave-dev] [jira] Commented: (JBEHAVE-161) HTML-based scenario reporting

[ http://jira.codehaus.org/browse/JBEHAVE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203676#action_203676 ] Mauro Talevi commented on JBEHAVE-161: -- Added HtmlPrintStreamScenarioReporter, providing

[jbehave-dev] [jira] Updated: (JBEHAVE-225) Multiline scenario title is parsed as empty

[ http://jira.codehaus.org/browse/JBEHAVE-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-225: - Description: If the scenario title (i.e. the text that follows the keyword Scenario) is over

[jbehave-dev] [jira] Resolved: (JBEHAVE-225) Multiline scenario title is parsed as empty

[ http://jira.codehaus.org/browse/JBEHAVE-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-225. -- Resolution: Fixed Multiline scenario title is parsed as empty

[jbehave-dev] [jira] Commented: (JBEHAVE-225) Multiline scenario title is parsed as empty

[ http://jira.codehaus.org/browse/JBEHAVE-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203737#action_203737 ] Mauro Talevi commented on JBEHAVE-225: -- Verified in

[jbehave-dev] [jira] Updated: (JBEHAVE-193) Cannot find the persistence.xml file

[ http://jira.codehaus.org/browse/JBEHAVE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-193: - Descoped until it can be reproduced and verified. Cannot find the persistence.xml file

[jbehave-dev] [jira] Updated: (JBEHAVE-193) Cannot find the persistence.xml file

[ http://jira.codehaus.org/browse/JBEHAVE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-193: - Comment: was deleted (was: Descoped until it can be reproduced and verified.) Cannot find the

[jbehave-dev] [jira] Updated: (JBEHAVE-193) Cannot find the persistence.xml file

[ http://jira.codehaus.org/browse/JBEHAVE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-193: - Fix Version/s: (was: 2.4) Descoped until it can be reproduced and verified. Cannot find the

[jbehave-dev] [jira] Resolved: (JBEHAVE-161) HTML-based scenario reporting

[ http://jira.codehaus.org/browse/JBEHAVE-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-161. -- Resolution: Fixed HTML-based scenario reporting -

[jbehave-dev] [jira] Resolved: (JBEHAVE-223) 0.0 gets parsed as a Long

[ http://jira.codehaus.org/browse/JBEHAVE-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-223. -- Resolution: Fixed Refactored NumberListConverter to use NumberFormat only when argument Type is

[jbehave-dev] [jira] Commented: (JBEHAVE-224) Double.NaN should be parseable into a double

[ http://jira.codehaus.org/browse/JBEHAVE-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203796#action_203796 ] Mauro Talevi commented on JBEHAVE-224: -- James, NaN and Infinity values are already supported

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

[ http://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203808#action_203808 ] Mauro Talevi commented on JBEHAVE-207: -- Actually, the Ant DirectoryScanner already has the SCM

[jbehave-dev] [jira] Created: (JBEHAVE-226) Statistics ScenarioReporter

Statistics ScenarioReporter --- Key: JBEHAVE-226 URL: http://jira.codehaus.org/browse/JBEHAVE-226 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi

[jbehave-dev] [jira] Resolved: (JBEHAVE-226) Statistics ScenarioReporter

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

[jbehave-dev] [jira] Updated: (JBEHAVE-165) Allow scenarios to run in batch mode

[ http://jira.codehaus.org/browse/JBEHAVE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-165: - Description: Currently, scenario fail in fail-fast mode (unless the ignoreFailure flag is enabled).

[jbehave-dev] [jira] Resolved: (JBEHAVE-165) Allow scenarios to run in batch mode

[ http://jira.codehaus.org/browse/JBEHAVE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-165. -- Resolution: Fixed Allow scenarios to run in batch mode

[jbehave-dev] [jira] Resolved: (JBEHAVE-203) StepsBehaviour tests fail with JDK 1.5

[ http://jira.codehaus.org/browse/JBEHAVE-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-203. -- Resolution: Fixed StepsBehaviour tests fail with JDK 1.5 ---

[jbehave-dev] [jira] Commented: (JBEHAVE-221) Maven runner documentation has incorrect capitalization (should be camel case)

[ http://jira.codehaus.org/browse/JBEHAVE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203917#action_203917 ] Mauro Talevi commented on JBEHAVE-221: -- This is an odd one. The source has correct

[jbehave-dev] [jira] Updated: (JBEHAVE-205) Is there a way to sync scenarios with classes?

[ http://jira.codehaus.org/browse/JBEHAVE-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-205: - Summary: Is there a way to sync scenarios with classes? (was: Is there a way to sync scenerios with

[jbehave-dev] [jira] Updated: (JBEHAVE-219) Create standard human and machine-readable reports

[ http://jira.codehaus.org/browse/JBEHAVE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-219: - Fix Version/s: 2.4 Create standard human and machine-readable reports

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-219) Create standard human and machine-readable reports

[ http://jira.codehaus.org/browse/JBEHAVE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=202231#action_202231 ] Mauro Talevi edited comment on JBEHAVE-219 at 12/23/09 3:06 AM: A

[jbehave-dev] [jira] Created: (JBEHAVE-227) XML Scenario Reporter

XML Scenario Reporter - Key: JBEHAVE-227 URL: http://jira.codehaus.org/browse/JBEHAVE-227 Project: JBehave Issue Type: New Feature Reporter: Mauro Talevi Assignee: Mauro Talevi Fix

[jbehave-dev] [jira] Resolved: (JBEHAVE-227) XML Scenario Reporter

[ http://jira.codehaus.org/browse/JBEHAVE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-227. -- Resolution: Fixed XML Scenario Reporter - Key: JBEHAVE-227

[jbehave-dev] [jira] Resolved: (JBEHAVE-219) Create standard human and machine-readable reports

[ http://jira.codehaus.org/browse/JBEHAVE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-219. -- Resolution: Fixed Create standard human and machine-readable reports

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-221) Maven runner documentation has incorrect capitalization (should be camel case)

[ http://jira.codehaus.org/browse/JBEHAVE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=203917#action_203917 ] Mauro Talevi edited comment on JBEHAVE-221 at 12/23/09 4:25 PM: The

[jbehave-dev] [jira] Updated: (JBEHAVE-221) Maven runner documentation has incorrect capitalization (should be camel case)

[ http://jira.codehaus.org/browse/JBEHAVE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-221: - Fix Version/s: 2.4 Assignee: Mauro Talevi Need to upgrade to latest version of

[jbehave-dev] [jira] Resolved: (JBEHAVE-221) Maven runner documentation has incorrect capitalization (should be camel case)

[ http://jira.codehaus.org/browse/JBEHAVE-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-221. -- Resolution: Fixed Maven runner documentation has incorrect capitalization (should be camel case)

[jbehave-dev] [jira] Resolved: (JBEHAVE-215) Allow a step to be reused between scenarios with and without example tables

[ http://jira.codehaus.org/browse/JBEHAVE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-215. -- Resolution: Won't Fix Refactored trader example to show that the same Java Steps methods (with

[jbehave-dev] [jira] Created: (JBEHAVE-228) ScenarioReporterBuilder

ScenarioReporterBuilder --- Key: JBEHAVE-228 URL: http://jira.codehaus.org/browse/JBEHAVE-228 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Assignee:

[jbehave-dev] [jira] Updated: (JBEHAVE-228) ScenarioReporterBuilder

[ http://jira.codehaus.org/browse/JBEHAVE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-228: - Description: A scenario reporter builder that allows easy instantiation of a delegating scenario

[jbehave-dev] [jira] Updated: (JBEHAVE-228) ScenarioReporterBuilder

[ http://jira.codehaus.org/browse/JBEHAVE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-228: - Description: A scenario reporter builder that allows easy instantiation of a delegating scenario

[jbehave-dev] [jira] Updated: (JBEHAVE-228) ScenarioReporterBuilder

[ http://jira.codehaus.org/browse/JBEHAVE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-228: - Description: A scenario reporter builder that allows easy instantiation of a delegating scenario

[jbehave-dev] [jira] Resolved: (JBEHAVE-228) ScenarioReporterBuilder

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

[jbehave-dev] [jira] Resolved: (JBEHAVE-229) PatternScenarioParser should depend on KeyWords and not Configuration

[ http://jira.codehaus.org/browse/JBEHAVE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-229. -- Resolution: Fixed PatternScenarioParser should depend on KeyWords and not Configuration

[jbehave-dev] [jira] Updated: (JBEHAVE-206) Regex overflow in using Examples table

[ http://jira.codehaus.org/browse/JBEHAVE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-206: - Fix Version/s: (was: 2.4) 2.5 Regex overflow in using Examples table

[jbehave-dev] [jira] Updated: (JBEHAVE-163) Support comments in plain-text scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-163: - Fix Version/s: (was: 2.4) 2.5 Support comments in plain-text scenarios

[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: - Component/s: Core Affects Version/s: 2.3 Fix Version/s: (was: 2.4)

[jbehave-dev] [jira] Created: (JBEHAVE-231) Allow CandidateSteps methods to be defined in POJOs

Allow CandidateSteps methods to be defined in POJOs --- Key: JBEHAVE-231 URL: http://jira.codehaus.org/browse/JBEHAVE-231 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Resolved: (JBEHAVE-231) Allow CandidateSteps methods to be defined in POJOs

[ http://jira.codehaus.org/browse/JBEHAVE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-231. -- Resolution: Fixed Allow CandidateSteps methods to be defined in POJOs

[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=206001#action_206001 ] Mauro Talevi commented on JBEHAVE-162: -- Added order_matching.scenario in trader example to

[jbehave-dev] [jira] Updated: (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 updated JBEHAVE-162: - Fix Version/s: (was: 2.4) 2.5 More investigation is needed, so descoping it

[jbehave-dev] [jira] Commented: (JBEHAVE-204) Scenario runner should report before and after story only once when running given scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=206003#action_206003 ] Mauro Talevi commented on JBEHAVE-204: -- Added given_non_successful.scenario that depends on a

[jbehave-dev] [jira] Resolved: (JBEHAVE-204) Scenario runner should report before and after story only once when running given scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-204. -- Resolution: Fixed Scenario runner should report before and after story only once when running

[jbehave-dev] [jira] Updated: (JBEHAVE-236) Checking out, building and testing JBehave from scratch

[ http://jira.codehaus.org/browse/JBEHAVE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-236: - Issue Type: Task (was: New Feature) Checking out, building and testing JBehave from scratch

[jbehave-dev] [jira] Commented: (JBEHAVE-236) Checking out, building and testing JBehave from scratch

[ http://jira.codehaus.org/browse/JBEHAVE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207862#action_207862 ] Mauro Talevi commented on JBEHAVE-236: -- Hi Liz, Ant build had out-of-date dependencies. I've

[jbehave-dev] [jira] Commented: (JBEHAVE-235) Improve documentation on running trader example with reports

[ http://jira.codehaus.org/browse/JBEHAVE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=207865#action_207865 ] Mauro Talevi commented on JBEHAVE-235: -- Added README.txt examples:

[jbehave-dev] [jira] Resolved: (JBEHAVE-235) Improve documentation on running trader example with reports

[ http://jira.codehaus.org/browse/JBEHAVE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-235. -- Resolution: Fixed Fix Version/s: 2.5 Improve documentation on running trader example with

[jbehave-dev] [jira] Updated: (JBEHAVE-236) Checking out, building and testing JBehave from scratch

[ http://jira.codehaus.org/browse/JBEHAVE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-236: - Fix Version/s: 2.5 Assignee: Mauro Talevi Checking out, building and testing JBehave from

[jbehave-dev] [jira] Created: (JBEHAVE-237) HTML/XML reports should handle better missing values from the examples table

HTML/XML reports should handle better missing values from the examples table - Key: JBEHAVE-237 URL: http://jira.codehaus.org/browse/JBEHAVE-237 Project: JBehave

[jbehave-dev] [jira] Updated: (JBEHAVE-237) HTML/XML reports should handle better missing or null values from the examples table

[ http://jira.codehaus.org/browse/JBEHAVE-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-237: - Description: Currently NPE can occur in escaping HTML/XML chars when the value for a given header is

[jbehave-dev] [jira] Updated: (JBEHAVE-163) Support comments in plain-text scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-163: - Component/s: Core Affects Version/s: (was: 2.2) 2.3 Fix

[jbehave-dev] [jira] Assigned: (JBEHAVE-163) Support comments in plain-text scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-163: Assignee: Mauro Talevi Support comments in plain-text scenarios

[jbehave-dev] [jira] Commented: (JBEHAVE-163) Support comments in plain-text scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209175#action_209175 ] Mauro Talevi commented on JBEHAVE-163: -- Added ignorable step type to allow comments, between

[jbehave-dev] [jira] Updated: (JBEHAVE-163) Support comments in plain-text scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-163: - Affects Version/s: (was: 2.3) 2.4 Support comments in plain-text

[jbehave-dev] [jira] Updated: (JBEHAVE-236) Checking out, building and testing JBehave from scratch

[ http://jira.codehaus.org/browse/JBEHAVE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-236: - Fix Version/s: 2.4.1 Checking out, building and testing JBehave from scratch

[jbehave-dev] [jira] Updated: (JBEHAVE-235) Improve documentation on running trader example with reports

[ http://jira.codehaus.org/browse/JBEHAVE-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-235: - Fix Version/s: 2.4.1 Improve documentation on running trader example with reports

[jbehave-dev] [jira] Created: (JBEHAVE-238) Provide default values for KeyWords, when not reading from a I18n bundle

Provide default values for KeyWords, when not reading from a I18n bundle Key: JBEHAVE-238 URL: http://jira.codehaus.org/browse/JBEHAVE-238 Project: JBehave Issue Type:

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-163) Support comments in plain-text scenarios

[ http://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209324#action_209324 ] Mauro Talevi edited comment on JBEHAVE-163 at 2/6/10 3:55 AM: -- As

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

Add @BeforeStory and @AfterStory annotations in candidate steps --- Key: JBEHAVE-239 URL: http://jira.codehaus.org/browse/JBEHAVE-239 Project: JBehave Issue Type: New Feature

[jbehave-dev] [jira] Work started: (JBEHAVE-133) Allow Steps dependencies to be composable via PicoContainer

[ http://jira.codehaus.org/browse/JBEHAVE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-133 started by Mauro Talevi. Allow Steps dependencies to be composable via PicoContainer ---

[jbehave-dev] [jira] Work started: (JBEHAVE-240) Allow Steps dependencies to be composable via Spring

[ http://jira.codehaus.org/browse/JBEHAVE-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-240 started by Mauro Talevi. Allow Steps dependencies to be composable via Spring

[jbehave-dev] [jira] Updated: (JBEHAVE-242) Regex Stackoverflow error with ExampleTables on Windows

[ http://jira.codehaus.org/browse/JBEHAVE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-242: - Fix Version/s: 2.5 Assignee: Mauro Talevi Regex Stackoverflow error with ExampleTables on

[jbehave-dev] [jira] Commented: (JBEHAVE-242) Regex Stackoverflow error with ExampleTables on Windows

[ http://jira.codehaus.org/browse/JBEHAVE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=209950#action_209950 ] Mauro Talevi commented on JBEHAVE-242: -- Applied, thanks! It passes all examples. I'd deploy a

[jbehave-dev] [jira] Resolved: (JBEHAVE-243) Get rid of trailing whitespaces after the table

[ http://jira.codehaus.org/browse/JBEHAVE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-243. -- Resolution: Fixed Applied trimming when parsing. Thanks. Get rid of trailing whitespaces after

[jbehave-dev] [jira] Assigned: (JBEHAVE-241) Allow Steps dependencies to be composable via Guice

[ http://jira.codehaus.org/browse/JBEHAVE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-241: Assignee: Mauro Talevi Allow Steps dependencies to be composable via Guice

[jbehave-dev] [jira] Work started: (JBEHAVE-241) Allow Steps dependencies to be composable via Guice

[ http://jira.codehaus.org/browse/JBEHAVE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-241 started by Mauro Talevi. Allow Steps dependencies to be composable via Guice --- Key:

[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] Resolved: (JBEHAVE-242) Regex Stackoverflow error with ExampleTables on Windows

[ http://jira.codehaus.org/browse/JBEHAVE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-242. -- Resolution: Fixed Regex Stackoverflow error with ExampleTables on Windows

[jbehave-dev] [jira] Resolved: (JBEHAVE-133) Allow Steps dependencies to be composable via PicoContainer

[ http://jira.codehaus.org/browse/JBEHAVE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-133. -- Resolution: Fixed Allow Steps dependencies to be composable via PicoContainer

[jbehave-dev] [jira] Resolved: (JBEHAVE-240) Allow Steps dependencies to be composable via Spring

[ http://jira.codehaus.org/browse/JBEHAVE-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-240. -- Resolution: Fixed Allow Steps dependencies to be composable via Spring

[jbehave-dev] [jira] Resolved: (JBEHAVE-241) Allow Steps dependencies to be composable via Guice

[ http://jira.codehaus.org/browse/JBEHAVE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-241. -- Resolution: Fixed Allow Steps dependencies to be composable via Guice

[jbehave-dev] [jira] Commented: (JBEHAVE-133) Allow Steps dependencies to be composable via PicoContainer

[ http://jira.codehaus.org/browse/JBEHAVE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=210726#action_210726 ] Mauro Talevi commented on JBEHAVE-133: -- Hi David, creating a scenario wrapper that does not

[jbehave-dev] [jira] Resolved: (JBEHAVE-206) Regex overflow in using Examples table

[ http://jira.codehaus.org/browse/JBEHAVE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-206. -- Resolution: Fixed Duplicate of JBEHAVE-242. Regex overflow in using Examples table

[jbehave-dev] [jira] Updated: (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 updated JBEHAVE-162: - Issue Type: Improvement (was: Bug) Reclassified from bug to enhancement. Need to be able to set

[jbehave-dev] [jira] Assigned: (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 reassigned JBEHAVE-230: Assignee: Mauro Talevi Add Narrative elements to Story parsing

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