Mauro Talevi (JIRA | 1 Nov 15:08 2009

[jira] Created: (JBEHAVE-199) Allow ScenarioClassLoader to instantiate scenarios using default constructor

Allow ScenarioClassLoader to instantiate scenarios using default constructor
----------------------------------------------------------------------------

                 Key: JBEHAVE-199
                 URL: http://jira.codehaus.org/browse/JBEHAVE-199
             Project: JBehave
          Issue Type: Improvement
          Components: Core
            Reporter: Mauro Talevi
            Priority: Minor
             Fix For: 2.4

Currently, all scenario classes need a constructor with a ClassLoader parameter, required by CLI runner
with Maven and Ant. 

While using core only, it is typically not required.  So ScenarioClassLoader.newScenario() should
support a varargs of parameter types, which also allow for no parameter types to instantiate using the
default constructor.    It is then up to the caller to use the appropriate parameter types. 

--

-- 
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
(Continue reading)

Mauro Talevi (JIRA | 1 Nov 15:12 2009

[jira] Resolved: (JBEHAVE-199) Allow ScenarioClassLoader to instantiate scenarios using default constructor


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

Mauro Talevi resolved JBEHAVE-199.
----------------------------------

    Resolution: Fixed

> Allow ScenarioClassLoader to instantiate scenarios using default constructor
> ----------------------------------------------------------------------------
>
>                 Key: JBEHAVE-199
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-199
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Mauro Talevi
>            Priority: Minor
>             Fix For: 2.4
>
>
> Currently, all scenario classes need a constructor with a ClassLoader parameter, required by CLI runner
with Maven and Ant. 
> While using core only, it is typically not required.  So ScenarioClassLoader.newScenario() should
support a varargs of parameter types, which also allow for no parameter types to instantiate using the
default constructor.    It is then up to the caller to use the appropriate parameter types. 

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

Mauro Talevi (JIRA | 2 Nov 18:23 2009

[jira] Updated: (JBEHAVE-199) Allow ScenarioClassLoader to instantiate scenarios using default constructor


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

Mauro Talevi updated JBEHAVE-199:
---------------------------------

    Fix Version/s: 2.3.2

> Allow ScenarioClassLoader to instantiate scenarios using default constructor
> ----------------------------------------------------------------------------
>
>                 Key: JBEHAVE-199
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-199
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Mauro Talevi
>            Priority: Minor
>             Fix For: 2.3.2, 2.4
>
>
> Currently, all scenario classes need a constructor with a ClassLoader parameter, required by CLI runner
with Maven and Ant. 
> While using core only, it is typically not required.  So ScenarioClassLoader.newScenario() should
support a varargs of parameter types, which also allow for no parameter types to instantiate using the
default constructor.    It is then up to the caller to use the appropriate parameter types. 

--

-- 
This message is automatically generated by JIRA.
(Continue reading)


Gmane