Paul Hammant <p...@...> writes: > > http://fisheye.codehaus.org/changelog/jbehave/?cs=1118 >
Pual, I think this page http://jbehave.org/documentation/regex-stack-overflow-errors/ would be better placed under FAQ or under a /known-issues parent page. Also, it'd be good if we added the link to the Sun JDK bug that is opened. I don't have it ATM but I can send it to you again if you can't find it. > I've seen this error in the field now and was able to breakpoint it. > Its going to suck a lot, unless we can come up with a number of > strategies for working around it. It's tricky because it's not really clear-cut when the regex bug kicks in. The strategies for working around it already exist and you started documenting them. I've found that the few times I've encountered this issue, a re-phrasing of the scenario steps, mostly trying to avoid duplication of steps, did the trick very well. We can expand on the page above given concrete examples and tips on how to re-phrase scenarios. Cheers --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
