[
http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235544#action_235544
]
Mauro Talevi commented on JBEHAVE-338:
--------------------------------------
Yes, it's essentially the pre-parsing concept proposed above.
But it's probably best done in a decorator class as it's a rather rare corner
case to justify it being done by default (would slow down parsing that is
already not lighting fast). Anybody wanting to use indentation could simply
configure the decorator around the regex story parser.
> Indented scenarios in stories was possible in JB2 but after upgrade failed in
> JB3
> ---------------------------------------------------------------------------------
>
> Key: JBEHAVE-338
> URL: http://jira.codehaus.org/browse/JBEHAVE-338
> Project: JBehave
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0
> Environment: Windows
> Reporter: Paul Hammant
> Priority: Minor
>
> A client had indented JB scenarios (tabs and/or spaces) in the .scenario
> files. When upgraded to JB3, and everything else was working for the renamed
> .story files. the scenarios were not being executed. It seems regex made no
> match.
> We had breakpoints in place so we could see the BeforeScenario being invoked,
> but none of the steps. When we removed the left-whitespace, it worked.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
