Development list for jBehave project

[jira] (JBEHAVE-716) Add an optional StoryFinder class parameter to @UsingPaths annotation

Cristiano Gavião created JBEHAVE-716:
----------------------------------------

             Summary: Add an optional StoryFinder class parameter to @UsingPaths annotation
                 Key: JBEHAVE-716
                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
             Project: JBehave
          Issue Type: New Feature
          Components: Core
            Reporter: Cristiano Gavião
             Fix For: 3.6

Currently @UsingPaths is using one fixed instance of StoryFinder class. 
In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinderClass parameter in the @UsingPaths annotation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.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

headers

Mauro Talevi (JIRA | 8 Feb 12:49

[jira] (JBEHAVE-716) Add an optional StoryFinder class parameter to @UsingPaths annotation


     [
https://jira.codehaus.org/browse/JBEHAVE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi reassigned JBEHAVE-716:
------------------------------------

    Assignee: Mauro Talevi

> Add an optional StoryFinder class parameter to @UsingPaths annotation
> ---------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Cristiano Gavião
>            Assignee: Mauro Talevi
>              Labels: annotation
>             Fix For: 3.6
>
>
> Currently @UsingPaths is using one fixed instance of StoryFinder class. 
> In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinderClass parameter in the @UsingPaths annotation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa

(Continue reading)

headers

Mauro Talevi (JIRA | 8 Feb 12:51

[jira] (JBEHAVE-716) Add an optional StoryFinder class element to @UsingPaths annotation


     [
https://jira.codehaus.org/browse/JBEHAVE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JBEHAVE-716 started by Mauro Talevi.

> Add an optional StoryFinder class element to @UsingPaths annotation
> -------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cristiano Gavião
>            Assignee: Mauro Talevi
>              Labels: annotation
>             Fix For: 3.6
>
>
> Currently @UsingPaths is using one fixed instance of StoryFinder class. 
> In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinder element in the @UsingPaths annotation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------

(Continue reading)

headers

Mauro Talevi (JIRA | 8 Feb 12:51

[jira] (JBEHAVE-716) Add an optional StoryFinder class element to @UsingPaths annotation


     [
https://jira.codehaus.org/browse/JBEHAVE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi updated JBEHAVE-716:
---------------------------------

    Description: 
Currently @UsingPaths is using one fixed instance of StoryFinder class. 
In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinder element in the @UsingPaths annotation.

  was:
Currently @UsingPaths is using one fixed instance of StoryFinder class. 
In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinderClass parameter in the @UsingPaths annotation.

     Issue Type: Improvement  (was: New Feature)
        Summary: Add an optional StoryFinder class element to @UsingPaths annotation  (was: Add an optional
StoryFinder class parameter to @UsingPaths annotation)

> Add an optional StoryFinder class element to @UsingPaths annotation
> -------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cristiano Gavião

(Continue reading)

headers

Mauro Talevi (JIRA | 11 Feb 18:04

[jira] (JBEHAVE-716) Add an optional StoryFinder class element to @UsingPaths annotation


     [
https://jira.codehaus.org/browse/JBEHAVE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi resolved JBEHAVE-716.
----------------------------------

    Resolution: Fixed

> Add an optional StoryFinder class element to @UsingPaths annotation
> -------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cristiano Gavião
>            Assignee: Mauro Talevi
>              Labels: annotation
>             Fix For: 3.6
>
>
> Currently @UsingPaths is using one fixed instance of StoryFinder class. 
> In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinder element in the @UsingPaths annotation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa

(Continue reading)

headers

Cristiano Gavião (JIRA | 14 Feb 15:41

[jira] (JBEHAVE-716) Add an optional StoryFinder class element to @UsingPaths annotation


     [
https://jira.codehaus.org/browse/JBEHAVE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cristiano Gavião reopened JBEHAVE-716:
--------------------------------------

Since we are informing the path and the StoryFinder class in the @UsingPaths, we need a
runStoriesAsPaths() method without parameter in Embedder class. 
Or perhaps a new Embedder abstract class that already implements the run() method of Embeddable interface.

> Add an optional StoryFinder class element to @UsingPaths annotation
> -------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cristiano Gavião
>            Assignee: Mauro Talevi
>              Labels: annotation
>             Fix For: 3.6
>
>
> Currently @UsingPaths is using one fixed instance of StoryFinder class. 
> In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinder element in the @UsingPaths annotation.

--

(Continue reading)

headers

Mauro Talevi (JIRA | 16 Feb 09:19

[jira] (JBEHAVE-716) Add an optional StoryFinder class element to @UsingPaths annotation


     [
https://jira.codehaus.org/browse/JBEHAVE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi resolved JBEHAVE-716.
----------------------------------

    Resolution: Fixed

@UsingPaths is used by the AnnotatedPathRunner and the paths configured are passed to the Embedder
runStoriesAsPaths(List<String>) method.

If you want, you can use the annotated builder to get the paths directly from the annotation. 

{code}
new AnnotationBuilder(A.class).findPaths()
{code}

We can devise other uses of @UsingPaths but it should be tracked by another Jira issue.

> Add an optional StoryFinder class element to @UsingPaths annotation
> -------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cristiano Gavião
>            Assignee: Mauro Talevi

(Continue reading)