[jbehave-dev] [jira] Updated: (JBEHAVE-127) Doesn't find scenarios with numbers in the file name

[ http://jira.codehaus.org/browse/JBEHAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-127: - Affects Version/s: 2.1 2.0.1 2.0 Doesn't find

[jbehave-scm] [1004] trunk/jbehave-core/src/java/org/jbehave/scenario/parser: JBEHAVE-127: Fixed bug that prevented use of numbers in the scenario file names.

Title: [1004] trunk/jbehave-core/src/java/org/jbehave/scenario/parser: JBEHAVE-127: Fixed bug that prevented use of numbers in the scenario file names. Revision 1004 Author mauro Date 2008-11-02 03:41:01 -0600 (Sun, 02 Nov 2008) Log Message JBEHAVE-127: Fixed bug that prevented use of

[jbehave-dev] [jira] Updated: (JBEHAVE-117) Should throw an exception if two candidate step methods have the same annotation

[ http://jira.codehaus.org/browse/JBEHAVE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-117: - Assignee: Mauro Talevi Affects Version/s: 2.1 2.0.1

[jbehave-scm] [1003] trunk/jbehave-core/src/behaviour/org/jbehave/scenario/steps: JBEHAVE-131: verify behaviour with multiple aliases.

Title: [1003] trunk/jbehave-core/src/behaviour/org/jbehave/scenario/steps: JBEHAVE-131: verify behaviour with multiple aliases. Revision 1003 Author mauro Date 2008-11-02 03:22:42 -0600 (Sun, 02 Nov 2008) Log Message JBEHAVE-131: verify behaviour with multiple aliases. Added aliases to

[jbehave-dev] [jira] Resolved: (JBEHAVE-131) Aliases for steps

[ http://jira.codehaus.org/browse/JBEHAVE-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-131. -- Resolution: Fixed Done - updated gameoflife and trader examples to use aliases. Aliases for steps

[jbehave-dev] [jira] Resolved: (JBEHAVE-144) Ensure utility methods should be independent of unit-testing framework

[ http://jira.codehaus.org/browse/JBEHAVE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-144. -- Resolution: Fixed Done - snapshots deployed. Please test with JUnit3. Ensure utility methods

[jbehave-dev] [jira] Updated: (JBEHAVE-130) Other examples include

[ http://jira.codehaus.org/browse/JBEHAVE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-130: - Affects Version/s: (was: 2.0) Other examples include --

[jbehave-dev] [jira] Updated: (JBEHAVE-144) Ensure utility methods should be independent of unit-testing framework

[ http://jira.codehaus.org/browse/JBEHAVE-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-144: - Assignee: Mauro Talevi Description: Refactor Ensure method to only depend on Hamcrest and

[jbehave-dev] [jira] Updated: (JBEHAVE-126) GivenScenarios

[ http://jira.codehaus.org/browse/JBEHAVE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-126: - Affects Version/s: 2.1 2.0.1 2.0 Fix Version/s:

[jbehave-scm] [1007] trunk/jbehave-core/src/java/org/jbehave/scenario/steps: JBEHAVE-117: Throws exception if duplicate candidate steps found.

Title: [1007] trunk/jbehave-core/src/java/org/jbehave/scenario/steps: JBEHAVE-117: Throws exception if duplicate candidate steps found. Revision 1007 Author mauro Date 2008-11-02 04:57:28 -0600 (Sun, 02 Nov 2008) Log Message JBEHAVE-117: Throws exception if duplicate candidate steps

[jbehave-scm] [1002] trunk/jbehave-core/src/java/org/jbehave: JBEHAVE-144: Refactored Ensure utility class to only depend on Hamcrest.

Title: [1002] trunk/jbehave-core/src/java/org/jbehave: JBEHAVE-144: Refactored Ensure utility class to only depend on Hamcrest. Revision 1002 Author mauro Date 2008-11-02 03:06:59 -0600 (Sun, 02 Nov 2008) Log Message JBEHAVE-144: Refactored Ensure utility class to only depend on

[jbehave-dev] [jira] Resolved: (JBEHAVE-117) Should throw an exception if two candidate step methods have the same annotation

[ http://jira.codehaus.org/browse/JBEHAVE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-117. -- Resolution: Fixed Throws runtime DuplicateCandidateStepFoundException if duplicate found. Should

[jbehave-dev] [jira] Updated: (JBEHAVE-127) Doesn't find scenarios with numbers in the file name

[ http://jira.codehaus.org/browse/JBEHAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-127: - Assignee: Mauro Talevi Fix Version/s: 2.2 Summary: Doesn't find scenarios with

[jbehave-dev] [jira] Resolved: (JBEHAVE-127) Doesn't find scenarios with numbers in the file name

[ http://jira.codehaus.org/browse/JBEHAVE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-127. -- Resolution: Fixed Done - snapshot deployed. Doesn't find scenarios with numbers in the file name

[jbehave-dev] [jira] Updated: (JBEHAVE-145) Unit-test runners should decorate Exceptions a bit more clearly

[ http://jira.codehaus.org/browse/JBEHAVE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-145: - Fix Version/s: 2.2 Summary: Unit-test runners should decorate Exceptions a bit more clearly

[jbehave-dev] [jira] Commented: (JBEHAVE-27) Document best practices and suggested use cases

[ http://jira.codehaus.org/browse/JBEHAVE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=152688#action_152688 ] Mauro Talevi commented on JBEHAVE-27: - Added page