[
http://jira.codehaus.org/browse/JBEHAVE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-248.
--
Resolution: Fixed
Should be able to use JBehave without inheriting from a base class
[
http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-156:
-
Description:
In order to avoid the need to define a Java class for each textual story
As a
[
http://jira.codehaus.org/browse/JBEHAVE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-287:
-
Fix Version/s: 2.5.6
Dry-run Scenario to determine that no steps are Pending
[
http://jira.codehaus.org/browse/JBEHAVE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reassigned JBEHAVE-287:
Assignee: Mauro Talevi
Dry-run Scenario to determine that no steps are Pending
[
http://jira.codehaus.org/browse/JBEHAVE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-287.
--
Resolution: Fixed
Added StepsConfiguration.doDryRun(boolean) method to control dry run mode.
[
http://jira.codehaus.org/browse/JBEHAVE-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-287:
-
Fix Version/s: 3.0
Dry-run Scenario to determine that no steps are Pending
[
http://jira.codehaus.org/browse/JBEHAVE-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-207.
--
Resolution: Won't Fix
Thanks for clarification. This seems to confirm that the issue is with the
Moved configuration and runner classes to separate packages
---
Key: JBEHAVE-289
URL: http://jira.codehaus.org/browse/JBEHAVE-289
Project: JBehave
Issue Type: Improvement
[
http://jira.codehaus.org/browse/JBEHAVE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=221693#action_221693
]
Mauro Talevi commented on JBEHAVE-288:
--
Precisely my point. One should be able to use any
Add method and steps instance information to matching events in StepsMonitor
Key: JBEHAVE-291
URL: http://jira.codehaus.org/browse/JBEHAVE-291
Project: JBehave
[
http://jira.codehaus.org/browse/JBEHAVE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-290.
--
Resolution: Fixed
Stack Overflow when parsing a scenario with a very long step
[
http://jira.codehaus.org/browse/JBEHAVE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-220:
-
Fix Version/s: 3.0
Allow per-scenario meta-information
---
Move I/O related components into separate package from parsing components
-
Key: JBEHAVE-293
URL: http://jira.codehaus.org/browse/JBEHAVE-293
Project: JBehave
Issue
Refactor step pattern parsing to allow non-regex implementations
-
Key: JBEHAVE-294
URL: http://jira.codehaus.org/browse/JBEHAVE-294
Project: JBehave
Issue Type: Improvement
[
http://jira.codehaus.org/browse/JBEHAVE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-294 started by Mauro Talevi.
Separate step pattern parsing from the matching
Key:
[
http://jira.codehaus.org/browse/JBEHAVE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reassigned JBEHAVE-294:
Assignee: Mauro Talevi
Separate step pattern parsing from the matching
[
http://jira.codehaus.org/browse/JBEHAVE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-294:
-
Summary: Separate step pattern parsing from the matching (was: Refactor
step pattern parsing to
[
http://jira.codehaus.org/browse/JBEHAVE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-293.
--
Resolution: Fixed
Move I/O related components into separate package from parsing components
[
http://jira.codehaus.org/browse/JBEHAVE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-289.
--
Resolution: Fixed
Moved configuration and runner classes to separate packages
[
http://jira.codehaus.org/browse/JBEHAVE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-294.
--
Resolution: Fixed
Separate step pattern parsing from the matching
[
http://jira.codehaus.org/browse/JBEHAVE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-256.
--
Resolution: Fixed
Stories should be retrievable from external or remote sources
Allow non-HTML file reports to be rendered undecorated with syntax highlighter
--
Key: JBEHAVE-295
URL: http://jira.codehaus.org/browse/JBEHAVE-295
Project: JBehave
[
http://jira.codehaus.org/browse/JBEHAVE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-295.
--
Resolution: Fixed
Set property decorateNonHtml=false in
[
http://jira.codehaus.org/browse/JBEHAVE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=222555#action_222555
]
Mauro Talevi commented on JBEHAVE-292:
--
I've verified that LoginProject works on Windows (XP)
Failure exception being thrown in PrintStream reporters prevents the delegating
reporter from completing
Key: JBEHAVE-296
URL:
[
http://jira.codehaus.org/browse/JBEHAVE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-296.
--
Resolution: Fixed
Failure exception being thrown in PrintStream reporters prevents the
[
http://jira.codehaus.org/browse/JBEHAVE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-296:
-
Description:
PrintStream reporters should not throw any exception upon step failures, since
they
GivenScenarios comma-separated paths should support newlines between paths
--
Key: JBEHAVE-297
URL: http://jira.codehaus.org/browse/JBEHAVE-297
Project: JBehave
Issue
CandidateStep finder
Key: JBEHAVE-298
URL: http://jira.codehaus.org/browse/JBEHAVE-298
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Mauro Talevi
Fix For: 3.0
Rename StepResult methods for consistency and clarity
-
Key: JBEHAVE-300
URL: http://jira.codehaus.org/browse/JBEHAVE-300
Project: JBehave
Issue Type: Improvement
Reporter:
Rename embeddedStory flag to givenStory in StoryRunner
--
Key: JBEHAVE-301
URL: http://jira.codehaus.org/browse/JBEHAVE-301
Project: JBehave
Issue Type: Improvement
Components:
Rename StepCreator to StepCollector
---
Key: JBEHAVE-302
URL: http://jira.codehaus.org/browse/JBEHAVE-302
Project: JBehave
Issue Type: Improvement
Components: Core
Reporter: Mauro Talevi
[
http://jira.codehaus.org/browse/JBEHAVE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-302:
-
Description:
CandidateStep is becoming too big and would benefit from a separation of
concern
[
http://jira.codehaus.org/browse/JBEHAVE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-302 started by Mauro Talevi.
Separate step matching from step creation in CandidateStep
--
[
http://jira.codehaus.org/browse/JBEHAVE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-302.
--
Resolution: Fixed
Separate step matching from step creation in CandidateStep
Improve reporting of failure
Key: JBEHAVE-305
URL: http://jira.codehaus.org/browse/JBEHAVE-305
Project: JBehave
Issue Type: Improvement
Components: Core
Reporter: Mauro Talevi
[
http://jira.codehaus.org/browse/JBEHAVE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-304:
-
Description:
When outputting example tables as parameters in HTML the newlines between rows
are
[
http://jira.codehaus.org/browse/JBEHAVE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-305 started by Mauro Talevi.
Improve reporting of failure
Key: JBEHAVE-305
URL:
[
http://jira.codehaus.org/browse/JBEHAVE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-304 started by Mauro Talevi.
Better rendering of ExamplesTable as parameter in HTML
--
[
http://jira.codehaus.org/browse/JBEHAVE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-305:
-
Description:
PrintStreamStoryReporter and subclasses have the reportErrors flag that prints
the
Remove redundant getter methods in RunnableStory
Key: JBEHAVE-307
URL: http://jira.codehaus.org/browse/JBEHAVE-307
Project: JBehave
Issue Type: Improvement
Components: Core
[
http://jira.codehaus.org/browse/JBEHAVE-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-267:
-
Description:
In 2.x, responsibilities are split between the StoryRunner and the Ant
task/Maven
[
http://jira.codehaus.org/browse/JBEHAVE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-308:
-
Description:
A better coordination of different configuration objects (for story, steps and
[
http://jira.codehaus.org/browse/JBEHAVE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-310.
--
Resolution: Fixed
Fix Version/s: 3.0
Rename failure handling strategies and implement as
[
http://jira.codehaus.org/browse/JBEHAVE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-308.
--
Resolution: Fixed
Consolidate configuration objects
-
[
http://jira.codehaus.org/browse/JBEHAVE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-303.
--
Resolution: Fixed
Mark start/end of all parameter values in step creation
[
http://jira.codehaus.org/browse/JBEHAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reopened JBEHAVE-307:
--
Remove redundant getter methods in RunnableStory
Pull up StepRunner and StepResult interfaces
Key: JBEHAVE-311
URL: http://jira.codehaus.org/browse/JBEHAVE-311
Project: JBehave
Issue Type: Improvement
Components: Core
Change terminology of report rendering to view generation
-
Key: JBEHAVE-313
URL: http://jira.codehaus.org/browse/JBEHAVE-313
Project: JBehave
Issue Type: Improvement
[
http://jira.codehaus.org/browse/JBEHAVE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-313:
-
Description:
To avoid confusion, change terminology reporting rendering to stories view
generation.
[
http://jira.codehaus.org/browse/JBEHAVE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-313.
--
Resolution: Fixed
Change terminology of report rendering to view generation
[
http://jira.codehaus.org/browse/JBEHAVE-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reassigned JBEHAVE-313:
Assignee: Mauro Talevi
Change terminology of report rendering to view generation
[
http://jira.codehaus.org/browse/JBEHAVE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-298.
--
Resolution: Fixed
CandidateStep finder
Key: JBEHAVE-298
[
http://jira.codehaus.org/browse/JBEHAVE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reassigned JBEHAVE-298:
Assignee: Mauro Talevi
CandidateStep finder
Key:
[
http://jira.codehaus.org/browse/JBEHAVE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-311.
--
Resolution: Fixed
Move step creation concern from Steps to StepCreator
[
http://jira.codehaus.org/browse/JBEHAVE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-274:
-
Component/s: Documentation
Description:
A SpringJUnit4ScenarioRunner example to show how the
[
http://jira.codehaus.org/browse/JBEHAVE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-314:
-
Summary: Use parameter language in place of arg in StepMonitor and
StepCreator (was: Rename
Rename StepMonitor and StepCreate to use parameter language in place of arg
---
Key: JBEHAVE-314
URL: http://jira.codehaus.org/browse/JBEHAVE-314
Project: JBehave
[
http://jira.codehaus.org/browse/JBEHAVE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-284:
-
Description:
Moving stories view generation concern to the embedder would allow the view to
be
[
http://jira.codehaus.org/browse/JBEHAVE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-263:
-
Description:
Right now the converters are called before running the scenario, which prevents
using
[
http://jira.codehaus.org/browse/JBEHAVE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-264:
-
Component/s: Core
Fix Version/s: 3.0
Steps could act as parameter converters : add the
[
http://jira.codehaus.org/browse/JBEHAVE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-264:
-
Description:
Better starting with an example :
{code}
Given a series
- Name : Series 0110
[
http://jira.codehaus.org/browse/JBEHAVE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=225879#action_225879
]
Mauro Talevi commented on JBEHAVE-264:
--
Hi Bruno, I've added the functionality to
[
http://jira.codehaus.org/browse/JBEHAVE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-264.
--
Resolution: Fixed
Steps methods as parameter converters when annotated by @AsParameterConverter
[
http://jira.codehaus.org/browse/JBEHAVE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-244:
-
Fix Version/s: (was: 3.1)
3.0
Step parameters should be converted just before
[
http://jira.codehaus.org/browse/JBEHAVE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-247:
-
Component/s: Core
Fix Version/s: (was: 3.1)
3.0
Summary:
[
http://jira.codehaus.org/browse/JBEHAVE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-150:
-
Description:
As a story developer, I want to load stories via URLs, not necessarily in the
[
http://jira.codehaus.org/browse/JBEHAVE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-150.
--
Resolution: Fixed
URL-based StoryLoader
-
Key: JBEHAVE-150
[
http://jira.codehaus.org/browse/JBEHAVE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-299.
--
Resolution: Not A Bug
Problems with jBehave, Maven and Windows
[
http://jira.codehaus.org/browse/JBEHAVE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-265:
-
Fix Version/s: (was: 3.1)
3.0
Allow annotation-based configuration
[
http://jira.codehaus.org/browse/JBEHAVE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-265 started by Mauro Talevi.
Allow annotation-based configuration
Key: JBEHAVE-265
[
http://jira.codehaus.org/browse/JBEHAVE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi reassigned JBEHAVE-265:
Assignee: Mauro Talevi
Allow annotation-based configuration
[
http://jira.codehaus.org/browse/JBEHAVE-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-254:
-
Description:
Story and steps configuration should be merged, maintaining what worked well
and
StoryPathFinder should normalised paths to always use '/' as separator
--
Key: JBEHAVE-318
URL: http://jira.codehaus.org/browse/JBEHAVE-318
Project: JBehave
Issue Type:
[
http://jira.codehaus.org/browse/JBEHAVE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-318:
-
Assignee: Mauro Talevi
Summary: StoryPathFinder should normalise paths with '/' as separator
StoryReporterBuilder should allow specification of Keywords
---
Key: JBEHAVE-319
URL: http://jira.codehaus.org/browse/JBEHAVE-319
Project: JBehave
Issue Type: Improvement
[
http://jira.codehaus.org/browse/JBEHAVE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-318.
--
Resolution: Fixed
StoryFinder should be responsible for finding story paths and runnable
stories
[
http://jira.codehaus.org/browse/JBEHAVE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=226414#action_226414
]
Mauro Talevi commented on JBEHAVE-317:
--
Can you use command-line properties, e.g. mvn install
[
http://jira.codehaus.org/browse/JBEHAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-307:
-
Description:
The name RunnableStory has become outdated and does not reflect the fact that
we can
[
http://jira.codehaus.org/browse/JBEHAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-307:
-
Summary: Rename RunnableStory - Embeddable and remove redundant methods
(was: Renamed interface
[
http://jira.codehaus.org/browse/JBEHAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-307:
-
Summary: Rename RunnableStory to Embeddable and remove redundant methods
(was: Rename RunnableStory
[
http://jira.codehaus.org/browse/JBEHAVE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-320.
--
Resolution: Fixed
Failures in step parametrisation are now caught and appropriate step results
[
http://jira.codehaus.org/browse/JBEHAVE-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-320:
-
Summary: @AfterStory method is not invoked is step parametrisation fails
(was: @AfterStory method is
Upgrade to new Codehaus release process
---
Key: JBEHAVE-321
URL: http://jira.codehaus.org/browse/JBEHAVE-321
Project: JBehave
Issue Type: Task
Reporter: Mauro Talevi
Assignee:
[
http://jira.codehaus.org/browse/JBEHAVE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-321:
-
Component/s: Build system
Upgrade to new Codehaus release process
Embedder should be responsible for instantiation of Embeddable instances
Key: JBEHAVE-322
URL: http://jira.codehaus.org/browse/JBEHAVE-322
Project: JBehave
Issue Type:
[
http://jira.codehaus.org/browse/JBEHAVE-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-322.
--
Resolution: Fixed
Embedder should be responsible for instantiation of Embeddable instances
[
http://jira.codehaus.org/browse/JBEHAVE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-321.
--
Resolution: Fixed
Upgrade to new Codehaus release process
---
[
http://jira.codehaus.org/browse/JBEHAVE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-275.
--
Resolution: Fixed
Ensure consistency of encoding
---
[
http://jira.codehaus.org/browse/JBEHAVE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-265.
--
Resolution: Fixed
Allow annotation-based configuration
[
http://jira.codehaus.org/browse/JBEHAVE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-323:
-
Description:
It is sometimes useful to invoke setup/teardown methods only once before and
after a
[
http://jira.codehaus.org/browse/JBEHAVE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-323.
--
Resolution: Fixed
Add @BeforeStories/@AfterStories annotations
Add methods in EmbedderMonitor to distinguish running an Embeddable from
running a story as path
Key: JBEHAVE-324
URL: http://jira.codehaus.org/browse/JBEHAVE-324
[
http://jira.codehaus.org/browse/JBEHAVE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=229989#action_229989
]
Mauro Talevi commented on JBEHAVE-328:
--
Hi Mike, thanks for the contributed patch. It looks
[
http://jira.codehaus.org/browse/JBEHAVE-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-325:
-
Description:
In some languages, e.g. Italian, Portuguese and Spanish, the And keyword is
translated
[
http://jira.codehaus.org/browse/JBEHAVE-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-325.
--
Resolution: Fixed
StoryParser should look for starting keywords only after a newline
[
http://jira.codehaus.org/browse/JBEHAVE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=230072#action_230072
]
Mauro Talevi commented on JBEHAVE-328:
--
Updated page to provide links to source repos for both
[
http://jira.codehaus.org/browse/JBEHAVE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=230221#action_230221
]
Mauro Talevi commented on JBEHAVE-327:
--
Actually, I'm having trouble applying them. My patch
[
http://jira.codehaus.org/browse/JBEHAVE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-327:
-
Affects Version/s: (was: 3.0)
Fix Version/s: 3.0
Assignee: Mauro Talevi
[
http://jira.codehaus.org/browse/JBEHAVE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=230340#action_230340
]
Mauro Talevi commented on JBEHAVE-327:
--
Applied patches 1 and 2 (after battling with issues
401 - 500 of 1926 matches
Mail list logo
