[jbehave-dev] [jira] Resolved: (JBEHAVE-521) Typo in jbehave-spring-archetype causes malformed pom.xml

[ http://jira.codehaus.org/browse/JBEHAVE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-521. -- Resolution: Fixed Typo in jbehave-spring-archetype causes malformed pom.xml

[jbehave-dev] [jira] Resolved: (JBEHAVE-522) Add documentation page on tutorials

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

[jbehave-dev] [jira] Updated: (JBEHAVE-520) NPE in StoryRunner: currentStrategy is not set when running before or after stories steps

[ http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-520: - Fix Version/s: (was: 3.4) 3.4.1 Summary: NPE in StoryRunner:

[jbehave-dev] [jira] Resolved: (JBEHAVE-520) NPE in StoryRunner: currentStrategy is not set when running before or after stories steps

[ http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-520. -- Resolution: Fixed NPE in StoryRunner: currentStrategy is not set when running before or after

[jbehave-dev] [jira] Updated: (JBEHAVE-520) StoryRunner failure strategy is not set when running before or after stories steps in multiple threads

[ http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-520: - Summary: StoryRunner failure strategy is not set when running before or after stories steps in

[jbehave-dev] [jira] Created: (JBEHAVE-523) Allow specification of Configuration implementation class via @Configure annotation

Allow specification of Configuration implementation class via @Configure annotation --- Key: JBEHAVE-523 URL: http://jira.codehaus.org/browse/JBEHAVE-523 Project:

[jbehave-dev] [jira] Created: (JBEHAVE-525) Add documentation page on tutorials

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

[jbehave-dev] [jira] Resolved: (JBEHAVE-525) Add documentation page on tutorials

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

[jbehave-dev] [jira] Updated: (JBEHAVE-524) Add page URL to screenshot console message

[ http://jira.codehaus.org/browse/JBEHAVE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-524: - Fix Version/s: web-3.3.4 Issue Type: Improvement (was: Bug) Summary: Add page URL to

[jbehave-dev] [jira] Created: (JBEHAVE-527) Composed steps not being matched when using non-named parameter matching for the composite step

Composed steps not being matched when using non-named parameter matching for the composite step --- Key: JBEHAVE-527 URL: http://jira.codehaus.org/browse/JBEHAVE-527

[jbehave-dev] [jira] Updated: (JBEHAVE-528) Examples Table for subset of steps

[ http://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-528: - Description: http://jbehave.org/reference/stable/tabular-parameters.html is great, but pertains to a

[jbehave-dev] [jira] Commented: (JBEHAVE-528) Examples Table for subset of steps

[ http://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=269442#action_269442 ] Mauro Talevi commented on JBEHAVE-528: -- Composite steps

[jbehave-dev] [jira] Resolved: (JBEHAVE-527) Composed steps not being matched when using non-named parameter matching for the composite step

[ http://jira.codehaus.org/browse/JBEHAVE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-527. -- Resolution: Fixed Composed steps not being matched when using non-named parameter matching for

[jbehave-dev] [jira] Created: (JBEHAVE-529) Simplify trader-ant example to not depend on the Maven pom.xml

Simplify trader-ant example to not depend on the Maven pom.xml -- Key: JBEHAVE-529 URL: http://jira.codehaus.org/browse/JBEHAVE-529 Project: JBehave Issue Type: Task

[jbehave-dev] [jira] Resolved: (JBEHAVE-529) Simplify trader-ant example to not depend on the Maven pom.xml

[ http://jira.codehaus.org/browse/JBEHAVE-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-529. -- Resolution: Fixed Simplify trader-ant example to not depend on the Maven pom.xml

[jbehave-dev] [jira] Updated: (JBEHAVE-514) jbehave-maven-plugin ignoring execution

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

[jbehave-dev] [jira] Resolved: (JBEHAVE-514) jbehave-maven-plugin ignoring execution

[ http://jira.codehaus.org/browse/JBEHAVE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-514. -- Resolution: Not A Bug Meta filters are documented here:

[jbehave-dev] [jira] Resolved: (JBEHAVE-414) Document generating StepDocs from a Embeddable instance

[ http://jira.codehaus.org/browse/JBEHAVE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-414. -- Resolution: Fixed Document generating StepDocs from a Embeddable instance

[jbehave-dev] [jira] Updated: (JBEHAVE-414) Document generating StepDocs from a Embeddable instance

[ http://jira.codehaus.org/browse/JBEHAVE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-414: - Fix Version/s: (was: 3.x) 3.4.3 Assignee: Mauro Talevi Document

[jbehave-dev] [jira] Created: (JBEHAVE-530) Add time duration to story statistics and reports view

Add time duration to story statistics and reports view -- Key: JBEHAVE-530 URL: http://jira.codehaus.org/browse/JBEHAVE-530 Project: JBehave Issue Type: Improvement Components:

[jbehave-dev] [jira] Resolved: (JBEHAVE-530) Add time duration to story statistics and reports view

[ http://jira.codehaus.org/browse/JBEHAVE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-530. -- Resolution: Fixed Add time duration to story statistics and reports view

[jbehave-dev] [jira] Updated: (JBEHAVE-521) Typo in jbehave-spring-archetype causes malformed pom.xml

[ http://jira.codehaus.org/browse/JBEHAVE-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-521: - Fix Version/s: 3.5 Typo in jbehave-spring-archetype causes malformed pom.xml

[jbehave-dev] [jira] Updated: (JBEHAVE-522) Add documentation page on tutorials

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

[jbehave-dev] [jira] Updated: (JBEHAVE-520) StoryRunner failure strategy is not set when running before or after stories steps in multiple threads

[ http://jira.codehaus.org/browse/JBEHAVE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-520: - Fix Version/s: 3.5 StoryRunner failure strategy is not set when running before or after stories

[jbehave-dev] [jira] Updated: (JBEHAVE-523) Allow specification of Configuration implementation class via @Configure annotation

[ http://jira.codehaus.org/browse/JBEHAVE-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-523: - Fix Version/s: 3.5 Allow specification of Configuration implementation class via @Configure

[jbehave-dev] [jira] Created: (JBEHAVE-531) OutcomesTable not being reported

OutcomesTable not being reported Key: JBEHAVE-531 URL: http://jira.codehaus.org/browse/JBEHAVE-531 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.4, 3.3

[jbehave-dev] [jira] Resolved: (JBEHAVE-531) OutcomesTable not being reported

[ http://jira.codehaus.org/browse/JBEHAVE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-531. -- Resolution: Fixed OutcomesTable not being reported

[jbehave-dev] [jira] Created: (JBEHAVE-532) Upgrade to hamcrest-library 1.2

Upgrade to hamcrest-library 1.2 --- Key: JBEHAVE-532 URL: http://jira.codehaus.org/browse/JBEHAVE-532 Project: JBehave Issue Type: Task Components: Core Affects Versions: 3.4 Reporter:

[jbehave-dev] [jira] Updated: (JBEHAVE-532) Split hamcrest-all dependency

[ http://jira.codehaus.org/browse/JBEHAVE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-532: - Description: From 1.2.x Hamcrest has removed hamcrest-all and moved to separate modules

[jbehave-dev] [jira] Resolved: (JBEHAVE-532) Split hamcrest-all dependency

[ http://jira.codehaus.org/browse/JBEHAVE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-532. -- Resolution: Fixed Split hamcrest-all dependency -

[jbehave-dev] [jira] Updated: (JBEHAVE-532) Split hamcrest-all dependency

[ http://jira.codehaus.org/browse/JBEHAVE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-532: - Description: From 1.2.x Hamcrest has removed hamcrest-all. As for 1.1 separate modules are

[jbehave-dev] [jira] Commented: (JBEHAVE-533) Bad encoding in JBehave Raports with default configuration from jbehave archetype in Windows

[ http://jira.codehaus.org/browse/JBEHAVE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=270075#action_270075 ] Mauro Talevi commented on JBEHAVE-533: -- Hi, so you seem to be using PL chars in the textual

[jbehave-dev] [jira] Created: (JBEHAVE-534) Lazy instantiation of steps classes, only if candidate steps are matched

Lazy instantiation of steps classes, only if candidate steps are matched Key: JBEHAVE-534 URL: http://jira.codehaus.org/browse/JBEHAVE-534 Project: JBehave Issue Type:

[jbehave-dev] [jira] Work started: (JBEHAVE-534) Lazy instantiation of steps classes, only if candidate steps are matched

[ http://jira.codehaus.org/browse/JBEHAVE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-534 started by Mauro Talevi. Lazy instantiation of steps classes, only if candidate steps are matched

[jbehave-dev] [jira] Created: (JBEHAVE-536) Allow stories that don't match filters not to be reported

Allow stories that don't match filters not to be reported - Key: JBEHAVE-536 URL: http://jira.codehaus.org/browse/JBEHAVE-536 Project: JBehave Issue Type: Improvement Affects

[jbehave-dev] [jira] Created: (JBEHAVE-537) Pluggable template processor for view generator

Pluggable template processor for view generator Key: JBEHAVE-537 URL: http://jira.codehaus.org/browse/JBEHAVE-537 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Work started: (JBEHAVE-535) Template-based reporters

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

[jbehave-dev] [jira] Updated: (JBEHAVE-537) Pluggable template processor for view generator

[ http://jira.codehaus.org/browse/JBEHAVE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-537: - Fix Version/s: 3.5 Pluggable template processor for view generator

[jbehave-dev] [jira] Work started: (JBEHAVE-537) Pluggable template processor for view generator

[ http://jira.codehaus.org/browse/JBEHAVE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-537 started by Mauro Talevi. Pluggable template processor for view generator Key:

[jbehave-dev] [jira] Updated: (JBEHAVE-539) ConcurrentModificationException in xref when run multithreaded.

[ http://jira.codehaus.org/browse/JBEHAVE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-539: - Fix Version/s: 3.5 Assignee: Paul Hammant ConcurrentModificationException in xref when run

[jbehave-dev] [jira] Commented: (JBEHAVE-538) Wrong encoding in reports running from JUnit (maven failsafe or surefire plugin, not dedicated jebhave maven plugin) on Windows

[ http://jira.codehaus.org/browse/JBEHAVE-538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=270888#comment-270888 ] Mauro Talevi commented on JBEHAVE-538: -- Why do you say that encoding issues only occur when

[jbehave-dev] [jira] Created: (JBEHAVE-540) Color-coded console output

Color-coded console output -- Key: JBEHAVE-540 URL: https://jira.codehaus.org/browse/JBEHAVE-540 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talevi Fix

[jbehave-dev] [jira] Updated: (JBEHAVE-540) ANSI-coded console output

[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-540: - Description: As contributed by Adriano Bonat:

[jbehave-dev] [jira] Commented: (JBEHAVE-541) Meta tags (and other things) injectable into components

[ https://jira.codehaus.org/browse/JBEHAVE-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=271134#comment-271134 ] Mauro Talevi commented on JBEHAVE-541: -- What are the usecases you are trying to address?

[jbehave-dev] [jira] Commented: (JBEHAVE-544) JBehave !-- Comments amongst meta tags causes corrupt XML output

[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=271136#comment-271136 ] Mauro Talevi commented on JBEHAVE-544: -- The syntax of meta do not recognise !-- at the

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-544) JBehave !-- Comments amongst meta tags causes corrupt XML output

[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=271136#comment-271136 ] Mauro Talevi edited comment on JBEHAVE-544 at 6/22/11 1:47 PM: --- The

[jbehave-dev] [jira] Commented: (JBEHAVE-544) JBehave !-- Comments amongst meta tags causes corrupt XML output

[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=271138#comment-271138 ] Mauro Talevi commented on JBEHAVE-544: -- Can you provide an example of an invalid XML and how

[jbehave-dev] [jira] Updated: (JBEHAVE-544) Ignore !-- comments in story meta

[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-544: - Description: Jenkins barfs when finding !-- during the XSLT transform (xUnit plugin). Can we

[jbehave-dev] [jira] Resolved: (JBEHAVE-544) Ignore !-- comments in story meta

[ https://jira.codehaus.org/browse/JBEHAVE-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-544. -- Resolution: Fixed Anything after ignorable keyword (!-- by default) is ignored in meta properties.

[jbehave-dev] [jira] Resolved: (JBEHAVE-546) Reports are not showing properly, all are showing as Zero

[ https://jira.codehaus.org/browse/JBEHAVE-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-546. -- Resolution: Not A Bug Fix Version/s: 3.5 You're missing the stats, which are used in the

[jbehave-dev] [jira] Updated: (JBEHAVE-547) StoryRunner.runParametrisedScenariosByExamples does not execute the examples after the first failure

[ https://jira.codehaus.org/browse/JBEHAVE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-547: - Fix Version/s: 3.5 StoryRunner.runParametrisedScenariosByExamples does not execute the examples

[jbehave-dev] [jira] Resolved: (JBEHAVE-547) StoryRunner.runParametrisedScenariosByExamples does not execute the examples after the first failure

[ https://jira.codehaus.org/browse/JBEHAVE-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-547. -- Resolution: Fixed StoryRunner.runParametrisedScenariosByExamples does not execute the examples

[jbehave-dev] [jira] Commented: (JBEHAVE-550) StoryReporterBuilder does not have an easy way to provide custom StoryReporter(s)

[ https://jira.codehaus.org/browse/JBEHAVE-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272004#comment-272004 ] Mauro Talevi commented on JBEHAVE-550: -- The StoryReporterBuilder provides the method

[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272240#comment-272240 ] Mauro Talevi commented on JBEHAVE-543: -- Thanks Adriano, looks like some nice very work at

[jbehave-dev] [jira] Updated: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-543: - Fix Version/s: 3.5 Assignee: Mauro Talevi Before/After Story/Scenario methods could accept

[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272629#comment-272629 ] Mauro Talevi commented on JBEHAVE-543: -- Adriano, I pulled your commits (except the one above)

[jbehave-dev] [jira] Work started: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-543 started by Mauro Talevi. Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[jbehave-dev] [jira] Work started: (JBEHAVE-540) ANSI-coded console output

[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-540 started by Mauro Talevi. ANSI-coded console output - Key: JBEHAVE-540 URL:

[jbehave-dev] [jira] Updated: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-543: - Component/s: Core Before/After Story/Scenario methods could accept parameters that have meaning

[jbehave-dev] [jira] Assigned: (JBEHAVE-540) ANSI-coded console output

[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-540: Assignee: Mauro Talevi ANSI-coded console output -

[jbehave-dev] [jira] Updated: (JBEHAVE-551) Better integration with JUnit (Separate results for each story/scenario/example)

[ https://jira.codehaus.org/browse/JBEHAVE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-551: - Fix Version/s: 3.5 Assignee: Mauro Talevi Better integration with JUnit (Separate results

[jbehave-dev] [jira] Updated: (JBEHAVE-528) Examples Table for subset of steps

[ https://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-528: - Fix Version/s: (was: 3.5) 3.x Examples Table for subset of steps

[jbehave-dev] [jira] Created: (JBEHAVE-553) Upgrade to Weld 1.1.1

Upgrade to Weld 1.1.1 - Key: JBEHAVE-553 URL: https://jira.codehaus.org/browse/JBEHAVE-553 Project: JBehave Issue Type: Improvement Components: Weld Support Reporter: Mauro Talevi

[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272741#comment-272741 ] Mauro Talevi commented on JBEHAVE-543: -- Upgraded to Weld 1.1.1 in JBEHAVE-553.

[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272746#comment-272746 ] Mauro Talevi commented on JBEHAVE-543: -- Pulled commits into master up to

[jbehave-dev] [jira] Created: (JBEHAVE-554) Upgrade to Selenium 2.0.0 final

Upgrade to Selenium 2.0.0 final --- Key: JBEHAVE-554 URL: https://jira.codehaus.org/browse/JBEHAVE-554 Project: JBehave Issue Type: Task Components: Web Selenium Reporter: Mauro Talevi

[jbehave-dev] [jira] Updated: (JBEHAVE-548) @BeforeExample und @AfterExample

[ https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-548: - Fix Version/s: 3.5 @BeforeExample und @AfterExample

[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273226#comment-273226 ] Mauro Talevi commented on JBEHAVE-543: -- Hi Adriano, I've pulled your commits. Did not see any

[jbehave-dev] [jira] Updated: (JBEHAVE-374) Upgrade to commons-lang 3.0 to correctly escape characters from the Unicode Supplemental Multilingual Plane

[ https://jira.codehaus.org/browse/JBEHAVE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-374: - Fix Version/s: (was: 3.x) 3.5 Assignee: Mauro Talevi Upgrade to

[jbehave-dev] [jira] Created: (JBEHAVE-558) Maven build should be updated to play well with Eclipse m2e 1.0

Maven build should be updated to play well with Eclipse m2e 1.0 --- Key: JBEHAVE-558 URL: https://jira.codehaus.org/browse/JBEHAVE-558 Project: JBehave Issue Type: Task

[jbehave-dev] [jira] Work started: (JBEHAVE-558) Maven build should be updated to play well with Eclipse m2e 1.0

[ https://jira.codehaus.org/browse/JBEHAVE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-558 started by Mauro Talevi. Maven build should be updated to play well with Eclipse m2e 1.0

[jbehave-dev] [jira] Created: (JBEHAVE-564) Update Ant and Maven configuration documentation

Update Ant and Maven configuration documentation - Key: JBEHAVE-564 URL: https://jira.codehaus.org/browse/JBEHAVE-564 Project: JBehave Issue Type: Task Components: Documentation

[jbehave-dev] [jira] Created: (JBEHAVE-565) Make public StoryRunner.State interface

Make public StoryRunner.State interface Key: JBEHAVE-565 URL: https://jira.codehaus.org/browse/JBEHAVE-565 Project: JBehave Issue Type: Task Components: Core Reporter: Mauro

[jbehave-dev] [jira] Resolved: (JBEHAVE-565) Make public StoryRunner.State interface

[ https://jira.codehaus.org/browse/JBEHAVE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-565. -- Resolution: Fixed Make public StoryRunner.State interface

[jbehave-dev] [jira] Updated: (JBEHAVE-567) Excluded (filtered-out) scenarios are reported as pending as well

[ https://jira.codehaus.org/browse/JBEHAVE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-567: - Fix Version/s: 3.5 Assignee: Mauro Talevi Excluded (filtered-out) scenarios are reported

[jbehave-dev] [jira] Resolved: (JBEHAVE-570) Excluded scenarios should not be included into ScenarioSuccessful count

[ https://jira.codehaus.org/browse/JBEHAVE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-570. -- Resolution: Fixed Fix Version/s: 3.5 Applied patch with thanks. Excluded scenarios should

[jbehave-dev] [jira] Created: (JBEHAVE-571) Shorten method and annotation signature in BeforeOrAfterFalled message

Shorten method and annotation signature in BeforeOrAfterFalled message -- Key: JBEHAVE-571 URL: https://jira.codehaus.org/browse/JBEHAVE-571 Project: JBehave Issue Type:

[jbehave-dev] [jira] Work started: (JBEHAVE-571) Compatify method and annotation information in BeforeOrAfterFalled message

[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-571 started by Mauro Talevi. Compatify method and annotation information in BeforeOrAfterFalled message

[jbehave-dev] [jira] Updated: (JBEHAVE-571) Compatify method and annotation information in BeforeOrAfterFalled message

[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-571: - Summary: Compatify method and annotation information in BeforeOrAfterFalled message (was: Shorten

[jbehave-dev] [jira] Updated: (JBEHAVE-571) Compactify method and annotation information in BeforeOrAfterFalled message

[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-571: - Summary: Compactify method and annotation information in BeforeOrAfterFalled message (was:

[jbehave-dev] [jira] Resolved: (JBEHAVE-557) When story has multiple failed scenarios, only one screenshot is created

[ https://jira.codehaus.org/browse/JBEHAVE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-557. -- Resolution: Fixed Pulled commit:

[jbehave-dev] [jira] Updated: (JBEHAVE-557) When story has multiple failed scenarios, only one screenshot is created

[ https://jira.codehaus.org/browse/JBEHAVE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-557: - Fix Version/s: 3.5 When story has multiple failed scenarios, only one screenshot is created

[jbehave-dev] [jira] Commented: (JBEHAVE-573) Step Marked as PENDING without preceding FAILED step - silent failure???

[ https://jira.codehaus.org/browse/JBEHAVE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=274889#comment-274889 ] Mauro Talevi commented on JBEHAVE-573: -- What's the usecase for the different method

[jbehave-dev] [jira] Created: (JBEHAVE-577) Flash support

Flash support - Key: JBEHAVE-577 URL: https://jira.codehaus.org/browse/JBEHAVE-577 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Mauro Talevi

[jbehave-dev] [jira] Updated: (JBEHAVE-575) Upgrade Selenium to 2.3.1

[ https://jira.codehaus.org/browse/JBEHAVE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-575: - Fix Version/s: web-3.4 Upgrade Selenium to 2.3.1 - Key:

[jbehave-dev] [jira] Work started: (JBEHAVE-577) Flash support

[ https://jira.codehaus.org/browse/JBEHAVE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-577 started by Mauro Talevi. Flash support - Key: JBEHAVE-577 URL:

[jbehave-dev] [jira] Updated: (JBEHAVE-568) Selenium 2.1.0 upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-568: - Fix Version/s: web-3.4 Issue Type: Task (was: Improvement) Selenium 2.1.0 upgrade

[jbehave-dev] [jira] Resolved: (JBEHAVE-554) Upgrade to Selenium 2.0.0 final

[ https://jira.codehaus.org/browse/JBEHAVE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-554. -- Resolution: Fixed Upgrade to Selenium 2.0.0 final ---

[jbehave-dev] [jira] Updated: (JBEHAVE-568) Selenium 2.1.0 upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-568: - Component/s: Web Selenium Selenium 2.1.0 upgrade -- Key:

[jbehave-dev] [jira] Updated: (JBEHAVE-572) Selenium 2.2 upgrade.

[ https://jira.codehaus.org/browse/JBEHAVE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-572: - Fix Version/s: web-3.4 Selenium 2.2 upgrade. - Key:

[jbehave-dev] [jira] Updated: (JBEHAVE-572) Selenium 2.2 upgrade.

[ https://jira.codehaus.org/browse/JBEHAVE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-572: - Component/s: Web Selenium Selenium 2.2 upgrade. - Key:

[jbehave-dev] [jira] Updated: (JBEHAVE-576) Allow for setting of environment vars on Firefox binary (for DISPLAY amongst others)

[ https://jira.codehaus.org/browse/JBEHAVE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-576: - Fix Version/s: web-3.4 Allow for setting of environment vars on Firefox binary (for DISPLAY amongst

[jbehave-dev] [jira] Created: (JBEHAVE-578) Story execution not failing-fast when ignoreFailuresInStories=false

Story execution not failing-fast when ignoreFailuresInStories=false --- Key: JBEHAVE-578 URL: https://jira.codehaus.org/browse/JBEHAVE-578 Project: JBehave Issue Type: Bug

[jbehave-dev] [jira] Work started: (JBEHAVE-578) Story execution not failing-fast when ignoreFailuresInStories=false

[ https://jira.codehaus.org/browse/JBEHAVE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-578 started by Mauro Talevi. Story execution not failing-fast when ignoreFailuresInStories=false

[jbehave-dev] [jira] Updated: (JBEHAVE-582) Base WebDriverPage should implement HasCapabilities, JavascriptExecutor and HasInputDevices

[ https://jira.codehaus.org/browse/JBEHAVE-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-582: - Affects Version/s: (was: 3.5) Fix Version/s: (was: 3.5)

[jbehave-dev] [jira] Updated: (JBEHAVE-583) Of multiple exclusion meta filters only one is evaluated

[ https://jira.codehaus.org/browse/JBEHAVE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-583: - Fix Version/s: 3.5 Thanks, added test cases. Of multiple exclusion meta filters only one is

[jbehave-dev] [jira] Updated: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-584: - Assignee: Mauro Talevi Support loading stories from Google Docs

[jbehave-dev] [jira] Work started: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-584 started by Mauro Talevi. Support loading stories from Google Docs Key: JBEHAVE-584

[jbehave-dev] [jira] Resolved: (JBEHAVE-583) Of multiple exclusion meta filters only one is evaluated

[ https://jira.codehaus.org/browse/JBEHAVE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-583. -- Resolution: Fixed Assignee: Mauro Talevi Of multiple exclusion meta filters only one is

[jbehave-dev] [jira] Commented: (JBEHAVE-585) BeforeStories.xml can be zero length ( causing xUnit to fail a Jenkins job )

[ https://jira.codehaus.org/browse/JBEHAVE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=276738#comment-276738 ] Mauro Talevi commented on JBEHAVE-585: -- So what is the proposed fix from JBehave's pov (i.e.

<    5   6   7   8   9   10   11   12   13   14   >