[jbehave-dev] [jira] Created: (JBEHAVE-314) Rename StepMonitor and StepCreate to use "parameter" language in place of "arg"

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

[jbehave-dev] [jira] Resolved: (JBEHAVE-314) Use "parameter" language in place of "arg" in StepMonitor and StepCreator

[ http://jira.codehaus.org/browse/JBEHAVE-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-314. -- Resolution: Fixed > Use "parameter" language in place of "arg" in StepMonitor and StepCreator >

[jbehave-dev] [jira] Updated: (JBEHAVE-284) Allow embedder to generate stories view after running them

[ 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 genera

[jbehave-dev] [jira] Updated: (JBEHAVE-263) Allow lazy parameter convertion

[ 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 st

[jbehave-dev] [jira] Updated: (JBEHAVE-264) Steps could act as parameter converters : add the @ParameterConverter annotation

[ 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 @Parame

[jbehave-dev] [jira] Resolved: (JBEHAVE-263) Allow lazy parameter convertion

[ http://jira.codehaus.org/browse/JBEHAVE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-263. -- Resolution: Fixed > Allow lazy parameter convertion > --- > >

[jbehave-dev] [jira] Updated: (JBEHAVE-264) Steps methods as parameter converters when annotated by @AsParameterConverter

[ 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

[jbehave-dev] [jira] Created: (JBEHAVE-315) Make ParameterConverters to use builder-style paradigm and add DateConverter

Make ParameterConverters to use builder-style paradigm and add DateConverter Key: JBEHAVE-315 URL: http://jira.codehaus.org/browse/JBEHAVE-315 Project: JBehave Issu

[jbehave-dev] [jira] Resolved: (JBEHAVE-315) Make ParameterConverters to use builder-style paradigm and add DateConverter

[ http://jira.codehaus.org/browse/JBEHAVE-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-315. -- Resolution: Fixed > Make ParameterConverters to use builder-style paradigm and add DateConverter > -

[jbehave-dev] [jira] Commented: (JBEHAVE-264) Steps methods as parameter converters when annotated by @AsParameterConverter

[ http://jira.codehaus.org/browse/JBEHAVE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225879#action_225879 ] Mauro Talevi commented on JBEHAVE-264: -- Hi Bruno, I've added the functionality to AbstractSteps

[jbehave-dev] [jira] Resolved: (JBEHAVE-264) Steps methods as parameter converters when annotated by @AsParameterConverter

[ 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 >

[jbehave-dev] [jira] Updated: (JBEHAVE-244) Step parameters should be converted just before the step executes (not when the scenario is parsed)

[ 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

[jbehave-dev] [jira] Resolved: (JBEHAVE-244) Step parameters should be converted just before the step executes (not when the scenario is parsed)

[ http://jira.codehaus.org/browse/JBEHAVE-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-244. -- Resolution: Duplicate Fixed by JBEHAVE-263 and JBEHAVE-264. > Step parameters should be converted j

[jbehave-dev] [jira] Resolved: (JBEHAVE-247) jBehave should be more intelligent/flexible with regards to prioritisation of steps

[ http://jira.codehaus.org/browse/JBEHAVE-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-247. -- Resolution: Fixed Added injectable PrioritisingStrategy in StepFinder with default ByPriorityField

[jbehave-dev] [jira] Updated: (JBEHAVE-247) jBehave should be more intelligent/flexible with regards to prioritisation of steps

[ 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: jBehave

[jbehave-dev] [jira] Updated: (JBEHAVE-150) URL-based StoryLoader

[ 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 classpat

[jbehave-dev] [jira] Resolved: (JBEHAVE-150) URL-based StoryLoader

[ 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-1

[jbehave-dev] [jira] Resolved: (JBEHAVE-299) Problems with jBehave, Maven and Windows

[ 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 > -

[jbehave-dev] [jira] Updated: (JBEHAVE-265) Allow annotation-based configuration

[ 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 >

[jbehave-dev] [jira] Work started: (JBEHAVE-265) 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 >

[jbehave-dev] [jira] Assigned: (JBEHAVE-265) Allow annotation-based configuration

[ 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 >

[jbehave-dev] [jira] Updated: (JBEHAVE-254) Merge story/steps 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 removin

[jbehave-dev] [jira] Updated: (JBEHAVE-298) Add StepFinder

[ http://jira.codehaus.org/browse/JBEHAVE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-298: - Description: In order to avoid duplication of steps As a story writer I want to find all candidate ste

[jbehave-dev] [jira] Created: (JBEHAVE-318) StoryPathFinder should normalised paths to always use '/' as separator

StoryPathFinder should normalised paths to always use '/' as separator -- Key: JBEHAVE-318 URL: http://jira.codehaus.org/browse/JBEHAVE-318 Project: JBehave Issue Type: Impr

[jbehave-dev] [jira] Updated: (JBEHAVE-318) StoryPathFinder should normalise paths with '/' as separator

[ 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 (wa

[jbehave-dev] [jira] Created: (JBEHAVE-319) StoryReporterBuilder should allow specification of Keywords

StoryReporterBuilder should allow specification of Keywords --- Key: JBEHAVE-319 URL: http://jira.codehaus.org/browse/JBEHAVE-319 Project: JBehave Issue Type: Improvement Comp

[jbehave-dev] [jira] Resolved: (JBEHAVE-319) StoryReporterBuilder should allow specification of Keywords

[ http://jira.codehaus.org/browse/JBEHAVE-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-319. -- Resolution: Fixed > StoryReporterBuilder should allow specification of Keywords > --

[jbehave-dev] [jira] Resolved: (JBEHAVE-318) StoryFinder should be responsible for finding story paths and runnable stories

[ 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 > storie

[jbehave-dev] [jira] Updated: (JBEHAVE-318) StoryFinder should be responsible for finding story paths and runnable stories

[ http://jira.codehaus.org/browse/JBEHAVE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-318: - Component/s: Maven Plugin Ant extension Description: StoryFinder should be a faca

[jbehave-dev] [jira] Updated: (JBEHAVE-316) Define commom JAXB interfaces for systems to provide Features and its Stories and Scenarios to a JBehave runner.

[ http://jira.codehaus.org/browse/JBEHAVE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-316: - Fix Version/s: (was: 3.0) 3.1 > Define commom JAXB interfaces for systems to pr

[jbehave-dev] [jira] Commented: (JBEHAVE-317) Allow system property to ignore failures in Maven

[ http://jira.codehaus.org/browse/JBEHAVE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226414#action_226414 ] Mauro Talevi commented on JBEHAVE-317: -- Can you use command-line properties, e.g. mvn install -

[jbehave-dev] [jira] Updated: (JBEHAVE-307) Renamed interface RunnableStory -> Embeddable and remove redundant methods

[ 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 run

[jbehave-dev] [jira] Updated: (JBEHAVE-307) Rename RunnableStory -> Embeddable and remove redundant methods

[ 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 Runn

[jbehave-dev] [jira] Commented: (JBEHAVE-317) Allow system property to ignore failures in Maven

[ http://jira.codehaus.org/browse/JBEHAVE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226625#action_226625 ] Mauro Talevi commented on JBEHAVE-317: -- Yes, provided you've configured the use of Maven proper

[jbehave-dev] [jira] Updated: (JBEHAVE-307) Rename RunnableStory to Embeddable and remove redundant methods

[ 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 -

[jbehave-dev] [jira] Resolved: (JBEHAVE-320) @AfterStory method is not invoked is step parametrisation fails

[ 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 retu

[jbehave-dev] [jira] Updated: (JBEHAVE-320) @AfterStory method is not invoked is step parametrisation fails

[ 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

[jbehave-dev] [jira] Created: (JBEHAVE-321) Upgrade to new Codehaus release process

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: Maur

[jbehave-dev] [jira] Updated: (JBEHAVE-233) Eclipse plugin for navigating between textual and code steps

[ http://jira.codehaus.org/browse/JBEHAVE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-233: - There is already a LD prioritisation strategy (JBEHAVE-247) which can be injected in the StepFinder. new

[jbehave-dev] [jira] Updated: (JBEHAVE-275) Ensure consistency of encoding

[ http://jira.codehaus.org/browse/JBEHAVE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-275: - Description: In order to allow reliable and consistent support for non-English languages, a consist

[jbehave-dev] [jira] Updated: (JBEHAVE-275) Ensure consistency of encoding

[ http://jira.codehaus.org/browse/JBEHAVE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-275: - Description: In order to allow reliable and consistent support for non-English languages, a consisten

[jbehave-dev] [jira] Work started: (JBEHAVE-275) Ensure consistency of encoding

[ http://jira.codehaus.org/browse/JBEHAVE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-275 started by Mauro Talevi. > Ensure consistency of encoding > --- > > Key: JBEHAVE-275 > URL: ht

[jbehave-dev] [jira] Resolved: (JBEHAVE-307) Rename RunnableStory to Embeddable and remove redundant methods

[ http://jira.codehaus.org/browse/JBEHAVE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-307. -- Resolution: Fixed > Rename RunnableStory to Embeddable and remove redundant methods > --

[jbehave-dev] [jira] Work started: (JBEHAVE-321) Upgrade to new Codehaus release process

[ http://jira.codehaus.org/browse/JBEHAVE-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-321 started by Mauro Talevi. > Upgrade to new Codehaus release process > --- > > Key: JBEHAVE-321 >

[jbehave-dev] [jira] Updated: (JBEHAVE-321) Upgrade to new Codehaus release process

[ 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 >

[jbehave-dev] [jira] Created: (JBEHAVE-322) Embedder should be responsible for instantiation of Embeddable instances

Embedder should be responsible for instantiation of Embeddable instances Key: JBEHAVE-322 URL: http://jira.codehaus.org/browse/JBEHAVE-322 Project: JBehave Issue Type:

[jbehave-dev] [jira] Resolved: (JBEHAVE-322) Embedder should be responsible for instantiation of Embeddable instances

[ 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 > -

[jbehave-dev] [jira] Resolved: (JBEHAVE-321) Upgrade to new Codehaus release process

[ 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 > --

[jbehave-dev] [jira] Resolved: (JBEHAVE-275) Ensure consistency of encoding

[ 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 > --- > >

[jbehave-dev] [jira] Resolved: (JBEHAVE-257) Migration path from JBehave 2.x to JBehave 3.x

[ http://jira.codehaus.org/browse/JBEHAVE-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-257. -- Resolution: Fixed > Migration path from JBehave 2.x to JBehave 3.x > ---

[jbehave-dev] [jira] Created: (JBEHAVE-323) Add @BeforeRun/@AfterRun annotations

Add @BeforeRun/@AfterRun annotations Key: JBEHAVE-323 URL: http://jira.codehaus.org/browse/JBEHAVE-323 Project: JBehave Issue Type: New Feature Components: Core Reporter: Mauro Talev

[jbehave-dev] [jira] Resolved: (JBEHAVE-265) Allow annotation-based configuration

[ 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 > > >

[jbehave-dev] [jira] Updated: (JBEHAVE-323) Add @BeforeStories/@AfterStories annotations

[ 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 c

[jbehave-dev] [jira] Resolved: (JBEHAVE-323) Add @BeforeStories/@AfterStories annotations

[ 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 > -

[jbehave-dev] [jira] Created: (JBEHAVE-324) Add methods in EmbedderMonitor to distinguish running an Embeddable from running a story as path

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

[jbehave-dev] [jira] Created: (JBEHAVE-325) StoryParser should look for starting keywords only after a newline

StoryParser should look for starting keywords only after a newline -- Key: JBEHAVE-325 URL: http://jira.codehaus.org/browse/JBEHAVE-325 Project: JBehave Issue Type: Improvement

[jbehave-dev] [jira] Commented: (JBEHAVE-328) Creation of a new parser to support the tracking of line numbers in error reporting.

[ http://jira.codehaus.org/browse/JBEHAVE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229989#action_229989 ] Mauro Talevi commented on JBEHAVE-328: -- Hi Mike, thanks for the contributed patch. It looks ve

[jbehave-dev] [jira] Commented: (JBEHAVE-328) Creation of a new parser to support the tracking of line numbers in error reporting.

[ http://jira.codehaus.org/browse/JBEHAVE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229993#action_229993 ] Mauro Talevi commented on JBEHAVE-328: -- Hi Mike, svn is still the repo used for the last stab

[jbehave-dev] [jira] Updated: (JBEHAVE-325) StoryParser should look for starting keywords only after a newline

[ 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

[jbehave-dev] [jira] Resolved: (JBEHAVE-325) StoryParser should look for starting keywords only after a newline

[ 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 > ---

[jbehave-dev] [jira] Commented: (JBEHAVE-328) Creation of a new parser to support the tracking of line numbers in error reporting.

[ http://jira.codehaus.org/browse/JBEHAVE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230072#action_230072 ] Mauro Talevi commented on JBEHAVE-328: -- Updated page to provide links to source repos for both

[jbehave-dev] [jira] Commented: (JBEHAVE-327) Remove dependency on javassist by using standard JDK annotation functionality

[ http://jira.codehaus.org/browse/JBEHAVE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230221#action_230221 ] Mauro Talevi commented on JBEHAVE-327: -- Actually, I'm having trouble applying them. My patch b

[jbehave-dev] [jira] Updated: (JBEHAVE-327) Remove dependency on javassist by using standard JDK annotation functionality

[ 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 > Rem

[jbehave-dev] [jira] Commented: (JBEHAVE-327) Remove dependency on javassist by using standard JDK annotation functionality

[ http://jira.codehaus.org/browse/JBEHAVE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230340#action_230340 ] Mauro Talevi commented on JBEHAVE-327: -- Applied patches 1 and 2 (after battling with issues wit

[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-327) Remove dependency on javassist by using standard JDK annotation functionality

[ http://jira.codehaus.org/browse/JBEHAVE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230340#action_230340 ] Mauro Talevi edited comment on JBEHAVE-327 at 7/30/10 8:27 AM: --- Applie

[jbehave-dev] [jira] Created: (JBEHAVE-329) Add @Inherited annotation to control inheritance behaviour of annotated configuration

Add @Inherited annotation to control inheritance behaviour of annotated configuration - Key: JBEHAVE-329 URL: http://jira.codehaus.org/browse/JBEHAVE-329 Project: JBe

[jbehave-dev] [jira] Resolved: (JBEHAVE-327) Remove dependency on javassist by using standard JDK annotation functionality

[ http://jira.codehaus.org/browse/JBEHAVE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-327. -- Resolution: Fixed Resolving this issue, as the dependency on javassist as been removed. Inheritanc

[jbehave-dev] [jira] Resolved: (JBEHAVE-324) Add methods in EmbedderMonitor to distinguish running an Embeddable from running a story as path

[ http://jira.codehaus.org/browse/JBEHAVE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-324. -- Resolution: Fixed > Add methods in EmbedderMonitor to distinguish running an Embeddable from > runn

[jbehave-dev] [jira] Updated: (JBEHAVE-329) Add inherit* property for array-valued annotation property to control inheritance behaviour

[ http://jira.codehaus.org/browse/JBEHAVE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-329: - Description: As explained in JBEHAVE-327, it's useful to control inheritance behaviour. By default in

[jbehave-dev] [jira] Resolved: (JBEHAVE-329) Add inherit* property for array-valued annotation property to control inheritance behaviour

[ http://jira.codehaus.org/browse/JBEHAVE-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-329. -- Resolution: Fixed Applied solution 3a) as proposed. > Add inherit* property for array-valued annot

[jbehave-dev] [jira] Created: (JBEHAVE-330) Allow pluggable strategy to resolve file paths from story location

Allow pluggable strategy to resolve file paths from story location -- Key: JBEHAVE-330 URL: http://jira.codehaus.org/browse/JBEHAVE-330 Project: JBehave Issue Type: Improvement

[jbehave-dev] [jira] Resolved: (JBEHAVE-330) Allow pluggable strategy to resolve file paths from story location

[ http://jira.codehaus.org/browse/JBEHAVE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-330. -- Resolution: Fixed > Allow pluggable strategy to resolve file paths from story location > ---

[jbehave-dev] [jira] Commented: (JBEHAVE-312) Configuration option for non-greedy matchers for steps

[ http://jira.codehaus.org/browse/JBEHAVE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232636#action_232636 ] Mauro Talevi commented on JBEHAVE-312: -- The prioritisation strategy is now configurable in 3.x:

[jbehave-dev] [jira] Created: (JBEHAVE-332) Refactor NumberConverter to use injectable NumberFormat

Refactor NumberConverter to use injectable NumberFormat --- Key: JBEHAVE-332 URL: http://jira.codehaus.org/browse/JBEHAVE-332 Project: JBehave Issue Type: Improvement Components:

[jbehave-dev] [jira] Resolved: (JBEHAVE-332) Refactor NumberConverter to use injectable NumberFormat

[ http://jira.codehaus.org/browse/JBEHAVE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-332. -- Resolution: Fixed > Refactor NumberConverter to use injectable NumberFormat > --

[jbehave-dev] [jira] Updated: (JBEHAVE-333) Cannot use '?' character in step annotations, escaping in regex is not happening properly.

[ http://jira.codehaus.org/browse/JBEHAVE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-333: - Summary: Cannot use '?' character in step annotations, escaping in regex is not happening properly. (

[jbehave-dev] [jira] Commented: (JBEHAVE-331) Allow Step-level dependencies

[ http://jira.codehaus.org/browse/JBEHAVE-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233111#action_233111 ] Mauro Talevi commented on JBEHAVE-331: -- Yes, agreed, we need to continue the discussion as the

[jbehave-dev] [jira] Resolved: (JBEHAVE-334) Spring Security Example (contribution)

[ http://jira.codehaus.org/browse/JBEHAVE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-334. -- Resolution: Fixed Thanks Brian. Example added. > Spring Security Example (contribution) > ---

[jbehave-dev] [jira] Reopened: (JBEHAVE-251) Selenium (under JBehave control) needs to be able to be instansiable at Story as well as Scenario level

[ http://jira.codehaus.org/browse/JBEHAVE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-251: -- Assignee: Mauro Talevi (was: Paul Hammant) Issues should not be closed, but resolved. > Seleniu

[jbehave-dev] [jira] Resolved: (JBEHAVE-251) Selenium (under JBehave control) needs to be able to be instansiable at Story as well as Scenario level

[ http://jira.codehaus.org/browse/JBEHAVE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-251. -- Resolution: Fixed > Selenium (under JBehave control) needs to be able to be instansiable at Story >

[jbehave-dev] [jira] Updated: (JBEHAVE-220) Allow per-story and per-scenario meta-information

[ http://jira.codehaus.org/browse/JBEHAVE-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-220: - Priority: Major (was: Minor) Assignee: Mauro Talevi Issue Type: New Feature (was: Improve

[jbehave-dev] [jira] Updated: (JBEHAVE-234) Improve JUnit integration

[ http://jira.codehaus.org/browse/JBEHAVE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-234: - Component/s: Core > Improve JUnit integration > - > > Key: JBE

[jbehave-dev] [jira] Created: (JBEHAVE-335) Migrate to Wicket as web application framework

Migrate to Wicket as web application framework -- Key: JBEHAVE-335 URL: http://jira.codehaus.org/browse/JBEHAVE-335 Project: JBehave Issue Type: New Feature Components: Web Runner

[jbehave-dev] [jira] Work started: (JBEHAVE-335) Refactor Web Runner to use Wicket as web application framework

[ http://jira.codehaus.org/browse/JBEHAVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-335 started by Mauro Talevi. > Refactor Web Runner to use Wicket as web application framework > --

[jbehave-dev] [jira] Updated: (JBEHAVE-335) Refactor Web Runner to use Wicket as web application framework

[ http://jira.codehaus.org/browse/JBEHAVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-335: - Description: Wicket shares the same philosophy as Waffle (embeddable, pure Java, no XML) and has a wi

[jbehave-dev] [jira] Updated: (JBEHAVE-213) Scenario runner form submission should support both GET and POST methods

[ http://jira.codehaus.org/browse/JBEHAVE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-213: - Fix Version/s: (was: web-3.0) > Scenario runner form submission should support both GET and POST m

[jbehave-dev] [jira] Updated: (JBEHAVE-192) Allow both relative and full path views for file contents

[ http://jira.codehaus.org/browse/JBEHAVE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-192: - Fix Version/s: (was: web-3.0) > Allow both relative and full path views for file contents > --

[jbehave-dev] [jira] Updated: (JBEHAVE-187) Data archive file content should be displayed using relative paths

[ http://jira.codehaus.org/browse/JBEHAVE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-187: - Fix Version/s: (was: web-3.0) > Data archive file content should be displayed using relative paths

[jbehave-dev] [jira] Updated: (JBEHAVE-191) Data file view URLs need to escape non-valid characters

[ http://jira.codehaus.org/browse/JBEHAVE-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-191: - Fix Version/s: (was: web-3.0) Summary: Data file view URLs need to escape non-valid chara

[jbehave-dev] [jira] Assigned: (JBEHAVE-188) Allow viewing of unarchived file contents

[ http://jira.codehaus.org/browse/JBEHAVE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-188: Assignee: Mauro Talevi > Allow viewing of unarchived file contents > ---

[jbehave-dev] [jira] Resolved: (JBEHAVE-335) Refactor Web Runner to use Wicket as web application framework

[ http://jira.codehaus.org/browse/JBEHAVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-335. -- Resolution: Fixed > Refactor Web Runner to use Wicket as web application framework > ---

[jbehave-dev] [jira] Commented: (JBEHAVE-335) Refactor Web Runner to use Wicket as web application framework

[ http://jira.codehaus.org/browse/JBEHAVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235205#action_235205 ] Mauro Talevi commented on JBEHAVE-335: -- Brian, Wicket is not a pure MVC framework, but more a c

[jbehave-dev] [jira] Updated: (JBEHAVE-335) Migrate Web Runner to use Wicket as web application framework

[ http://jira.codehaus.org/browse/JBEHAVE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-335: - Summary: Migrate Web Runner to use Wicket as web application framework (was: Refactor Web Runner to u

[jbehave-dev] [jira] Resolved: (JBEHAVE-336) Find Steps page

[ http://jira.codehaus.org/browse/JBEHAVE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-336. -- Resolution: Fixed > Find Steps page > --- > > Key: JBEHAVE-336 >

[jbehave-dev] [jira] Created: (JBEHAVE-336) Find Steps page

Find Steps page --- Key: JBEHAVE-336 URL: http://jira.codehaus.org/browse/JBEHAVE-336 Project: JBehave Issue Type: New Feature Components: Web Runner Reporter: Mauro Talevi Assignee: Mauro Talevi

[jbehave-dev] [jira] Commented: (JBEHAVE-337) jbehave-maven-plugin thows NoClassDefFoundError org/apache/log4j/Priority when maven project includes log4j dependency

[ http://jira.codehaus.org/browse/JBEHAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235499#action_235499 ] Mauro Talevi commented on JBEHAVE-337: -- Add dependency to plugin rather than the project (see e

[jbehave-dev] [jira] Commented: (JBEHAVE-338) Indented scenarios in stories was possible in JB2 but after upgrade failed in JB3

[ http://jira.codehaus.org/browse/JBEHAVE-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235534#action_235534 ] Mauro Talevi commented on JBEHAVE-338: -- Brian is quite right - this is not a regression, rather

[jbehave-dev] [jira] Updated: (JBEHAVE-339) HTML report numbers could be more tabular

[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-339: - Description: guice.stories.simple_guice_example Scenarios: 1 (Failed: 0) Steps: 3 (Successful: 3

[jbehave-dev] [jira] Updated: (JBEHAVE-339) HTML report numbers could be more tabular

[ http://jira.codehaus.org/browse/JBEHAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-339: - Fix Version/s: 3.1 > HTML report numbers could be more tabular >

[jbehave-dev] [jira] Updated: (JBEHAVE-337) Document how to configure jbehave-maven-plugin to be aware of log4j dependency

[ http://jira.codehaus.org/browse/JBEHAVE-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-337: - Fix Version/s: 3.1 Issue Type: Task (was: Bug) Summary: Document how to configure jbe

<    3   4   5   6   7   8   9   10   11   12   >