[jbehave-dev] [jira] Created: (JBEHAVE-156) Allow resolution of multiple textual scenarios from a single Java scenario
Allow resolution of multiple textual scenarios from a single Java scenario -- Key: JBEHAVE-156 URL: http://jira.codehaus.org/browse/JBEHAVE-156 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 2.1 Reporter: Mauro Talevi Fix For: 2.2 As a scenario runner, I want to be able to run multiple textual scenarios from the same Java Scenario class, using a single Steps class instance that contains all my steps. We'd need to provide some way to configure which textual scenarios are to run. This would be useful as a start of a web or wiki-based scenario runner. -- 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
[jbehave-dev] [jira] Updated: (JBEHAVE-156) Allow resolution of multiple textual scenarios from a single Java scenario
[ http://jira.codehaus.org/browse/JBEHAVE-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-156: - Description: As a scenario runner, I want to be able to run multiple textual scenarios from the same Java Scenario class, using a single Steps class instance that contains all my steps. The main refactor (backward-compatible) would be to add a method to ScenarioNameResolver ListString resolveAll(Class? extends Scenario scenarioClass); which as a special case returns a single path. In the implementation we'd also need to provide some way to configure which textual scenarios are to run. This would be useful as a start of a web or wiki-based scenario runner. was: As a scenario runner, I want to be able to run multiple textual scenarios from the same Java Scenario class, using a single Steps class instance that contains all my steps. We'd need to provide some way to configure which textual scenarios are to run. This would be useful as a start of a web or wiki-based scenario runner. Allow resolution of multiple textual scenarios from a single Java scenario -- Key: JBEHAVE-156 URL: http://jira.codehaus.org/browse/JBEHAVE-156 Project: JBehave Issue Type: Improvement Components: Core Affects Versions: 2.1 Reporter: Mauro Talevi Fix For: 2.2 As a scenario runner, I want to be able to run multiple textual scenarios from the same Java Scenario class, using a single Steps class instance that contains all my steps. The main refactor (backward-compatible) would be to add a method to ScenarioNameResolver ListString resolveAll(Class? extends Scenario scenarioClass); which as a special case returns a single path. In the implementation we'd also need to provide some way to configure which textual scenarios are to run. This would be useful as a start of a web or wiki-based scenario runner. -- 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
[jbehave-dev] [jira] Updated: (JBEHAVE-155) Maven plugin can't identify Scenario classes in src/test/java
[
http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-155:
-
Summary: Maven plugin can't identify Scenario classes in src/test/java
(was: Mven plugin can't identify Scenario classes in src/test/java)
Thanks Binil - I'll try to reproduce it.
Maven plugin can't identify Scenario classes in src/test/java
-
Key: JBEHAVE-155
URL: http://jira.codehaus.org/browse/JBEHAVE-155
Project: JBehave
Issue Type: Bug
Components: Maven Plugin
Affects Versions: 2.1
Environment: Maven 2.0.9, Java 1.5.0_16
Reporter: Binil Thomas
Assignee: Mauro Talevi
Attachments: jbehave-bug-report.tar.gz
I have the JBehave Maven plugin configured with test scope. In 2.0.1, the
plugin was able to pick up the Scenario classes from src/test/java, but in
2.1 it fails to. Please try running the attached maven project with different
-Djbehave.version settings to reproduce the error.
$ mvn -Djbehave.version=2.0.1 clean integration-test
...
[INFO] [jbehave:run-scenarios {execution: run-scenarios-listed}]
[INFO] Running scenario binil.scenarios.MyScenario
...
$ mvn -Djbehave.version=2.1 clean integration-test
...
[INFO] [jbehave:run-scenarios {execution: run-scenarios-listed}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to instantiate scenario 'binil.scenarios.MyScenario'
Embedded error: The scenario 'binil.scenarios.MyScenario' could not be
instantiated with class loader: [org.jbehave.scenario.ScenarioClassLoader
urls=[/Users/binil/work/jbehave-bug-report/target/classes]]
--
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
[jbehave-dev] [jira] Updated: (JBEHAVE-155) Maven plugin can't identify Scenario classes in src/test/java
[
http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-155:
-
Fix Version/s: 2.1.1
Binil, confirmed and tracked down problem. Will release bugfix version 2.1.1
and merge changeset in trunk.
Maven plugin can't identify Scenario classes in src/test/java
-
Key: JBEHAVE-155
URL: http://jira.codehaus.org/browse/JBEHAVE-155
Project: JBehave
Issue Type: Bug
Components: Maven Plugin
Affects Versions: 2.1
Environment: Maven 2.0.9, Java 1.5.0_16
Reporter: Binil Thomas
Assignee: Mauro Talevi
Fix For: 2.1.1
Attachments: jbehave-bug-report.tar.gz
I have the JBehave Maven plugin configured with test scope. In 2.0.1, the
plugin was able to pick up the Scenario classes from src/test/java, but in
2.1 it fails to. Please try running the attached maven project with different
-Djbehave.version settings to reproduce the error.
$ mvn -Djbehave.version=2.0.1 clean integration-test
...
[INFO] [jbehave:run-scenarios {execution: run-scenarios-listed}]
[INFO] Running scenario binil.scenarios.MyScenario
...
$ mvn -Djbehave.version=2.1 clean integration-test
...
[INFO] [jbehave:run-scenarios {execution: run-scenarios-listed}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to instantiate scenario 'binil.scenarios.MyScenario'
Embedded error: The scenario 'binil.scenarios.MyScenario' could not be
instantiated with class loader: [org.jbehave.scenario.ScenarioClassLoader
urls=[/Users/binil/work/jbehave-bug-report/target/classes]]
--
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
[jbehave-scm] [1022] trunk/examples: JBEHAVE-155: Merged changeset 1021 from branches/jbehave-2.1.x to trunk.
Title: [1022] trunk/examples: JBEHAVE-155: Merged changeset 1021 from branches/jbehave-2.1.x to trunk.
Revision 1022
Author mauro
Date 2009-01-24 12:57:03 -0600 (Sat, 24 Jan 2009)
Log Message
JBEHAVE-155: Merged changeset 1021 from branches/jbehave-2.1.x to trunk.
Modified Paths
trunk/examples/pom.xml
trunk/jbehave-maven-plugin/src/main/java/org/jbehave/mojo/AbstractScenarioMojo.java
Added Paths
trunk/examples/trader-test-scope/
trunk/examples/trader-test-scope/pom.xml
Removed Paths
trunk/examples/trader-test-scope/pom.xml
Diff
Modified: trunk/examples/pom.xml (1021 => 1022)
--- trunk/examples/pom.xml 2009-01-24 18:46:36 UTC (rev 1021)
+++ trunk/examples/pom.xml 2009-01-24 18:57:03 UTC (rev 1022)
@@ -16,6 +16,7 @@
modulenoughtsandcrosses/module
modulenoughtsandcrosses/scenarios/module
moduletrader/module
+moduletrader-test-scope/module
/modules
dependencies
Copied: trunk/examples/trader-test-scope (from rev 1021, branches/jbehave-2.1.x/examples/trader-test-scope) ( => )
Property changes on: trunk/examples/trader-test-scope
___
Name: svn:ignore
+ target
Deleted: trunk/examples/trader-test-scope/pom.xml (1021 => 1022)
--- branches/jbehave-2.1.x/examples/trader-test-scope/pom.xml 2009-01-24 18:46:36 UTC (rev 1021)
+++ trunk/examples/trader-test-scope/pom.xml 2009-01-24 18:57:03 UTC (rev 1022)
@@ -1,63 +0,0 @@
-project xmlns=http://maven.apache.org/POM/4.0.0 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
- xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd
- modelVersion4.0.0/modelVersion
- parent
-groupIdorg.jbehave/groupId
-artifactIdjbehave-examples/artifactId
-version2.1.1-SNAPSHOT/version
- /parent
- artifactIdjbehave-trader-test-scope-example/artifactId
- nameJBehave Trader Test Scope Example/name
-
- build
-!-- JBEHAVE-155: we want to prove that we can run scenarios in test scope --
-testSourceDirectory${basedir}/../trader/src/main/java/testSourceDirectory
-plugins
- plugin
-groupIdorg.jbehave/groupId
-artifactIdjbehave-maven-plugin/artifactId
-version${pom.version}/version
-executions
- execution
-idrun-scenarios-found/id
-phaseintegration-test/phase
-configuration
- scenarioIncludes
-scenarioIncludeorg/jbehave/examples/trader/scenarios/*.java/scenarioInclude
- /scenarioIncludes
- scenarioExcludes
-scenarioExclude**/*Steps.java/scenarioExclude
- /scenarioExcludes
- skipfalse/skip
- scopetest/scope
-/configuration
-goals
- goalrun-scenarios/goal
-/goals
- /execution
-/executions
- /plugin
- plugin
-groupIdorg.apache.maven.plugins/groupId
-artifactIdmaven-antrun-plugin/artifactId
-executions
- execution
-idrun-scenarios-via-ant/id
-phaseintegration-test/phase
-configuration
- tasks
-taskdef name=scenarioRunner classname=org.jbehave.ant.ScenarioRunnerTask classpathref=maven.runtime.classpath /
-scenarioRunner scenarioIncludes=org/jbehave/examples/trader/scenarios/*.java
- scenarioExcludes=**/*Steps.java skip=false scope=test /
- /tasks
-/configuration
-goals
- goalrun/goal
-/goals
- /execution
-/executions
- /plugin
-
-/plugins
- /build
-/project
\ No newline at end of file
Copied: trunk/examples/trader-test-scope/pom.xml (from rev 1021, branches/jbehave-2.1.x/examples/trader-test-scope/pom.xml) (0 => 1022)
--- trunk/examples/trader-test-scope/pom.xml (rev 0)
+++ trunk/examples/trader-test-scope/pom.xml 2009-01-24 18:57:03 UTC (rev 1022)
@@ -0,0 +1,63 @@
+project xmlns=http://maven.apache.org/POM/4.0.0 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
+ xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd
+ modelVersion4.0.0/modelVersion
+ parent
+groupIdorg.jbehave/groupId
+artifactIdjbehave-examples/artifactId
+version2.2-SNAPSHOT/version
+ /parent
+ artifactIdjbehave-trader-test-scope-example/artifactId
+ nameJBehave Trader Test Scope Example/name
+
+ build
+!-- JBEHAVE-155: we want to prove that we can run scenarios in test scope --
+testSourceDirectory${basedir}/../trader/src/main/java/testSourceDirectory
+plugins
+ plugin
+groupIdorg.jbehave/groupId
+artifactIdjbehave-maven-plugin/artifactId
+version${pom.version}/version
+executions
+ execution
+idrun-scenarios-found/id
+phaseintegration-test/phase
+configuration
+
[jbehave-scm] [1023] branches/jbehave-2.1.x: [maven-release-plugin] prepare release jbehave-2.1.1
Title: [1023] branches/jbehave-2.1.x: [maven-release-plugin] prepare release jbehave-2.1.1 Revision 1023 Author mauro Date 2009-01-24 13:05:25 -0600 (Sat, 24 Jan 2009) Log Message [maven-release-plugin] prepare release jbehave-2.1.1 Modified Paths branches/jbehave-2.1.x/distribution/pom.xml branches/jbehave-2.1.x/jbehave-ant/pom.xml branches/jbehave-2.1.x/jbehave-core/pom.xml branches/jbehave-2.1.x/jbehave-maven-plugin/pom.xml branches/jbehave-2.1.x/pom.xml Diff Modified: branches/jbehave-2.1.x/distribution/pom.xml (1022 => 1023) --- branches/jbehave-2.1.x/distribution/pom.xml 2009-01-24 18:57:03 UTC (rev 1022) +++ branches/jbehave-2.1.x/distribution/pom.xml 2009-01-24 19:05:25 UTC (rev 1023) @@ -3,7 +3,7 @@ parent groupIdorg.jbehave/groupId artifactIdjbehave/artifactId -version2.1.1-SNAPSHOT/version +version2.1.1/version /parent artifactIdjbehave-distribution/artifactId packagingpom/packaging Modified: branches/jbehave-2.1.x/jbehave-ant/pom.xml (1022 => 1023) --- branches/jbehave-2.1.x/jbehave-ant/pom.xml 2009-01-24 18:57:03 UTC (rev 1022) +++ branches/jbehave-2.1.x/jbehave-ant/pom.xml 2009-01-24 19:05:25 UTC (rev 1023) @@ -3,7 +3,7 @@ parent groupIdorg.jbehave/groupId artifactIdjbehave/artifactId -version2.1.1-SNAPSHOT/version +version2.1.1/version /parent artifactIdjbehave-ant/artifactId nameJBehave Ant/name Modified: branches/jbehave-2.1.x/jbehave-core/pom.xml (1022 => 1023) --- branches/jbehave-2.1.x/jbehave-core/pom.xml 2009-01-24 18:57:03 UTC (rev 1022) +++ branches/jbehave-2.1.x/jbehave-core/pom.xml 2009-01-24 19:05:25 UTC (rev 1023) @@ -3,7 +3,7 @@ parent groupIdorg.jbehave/groupId artifactIdjbehave/artifactId -version2.1.1-SNAPSHOT/version +version2.1.1/version /parent packagingjar/packaging artifactIdjbehave-core/artifactId Modified: branches/jbehave-2.1.x/jbehave-maven-plugin/pom.xml (1022 => 1023) --- branches/jbehave-2.1.x/jbehave-maven-plugin/pom.xml 2009-01-24 18:57:03 UTC (rev 1022) +++ branches/jbehave-2.1.x/jbehave-maven-plugin/pom.xml 2009-01-24 19:05:25 UTC (rev 1023) @@ -3,7 +3,7 @@ parent groupIdorg.jbehave/groupId artifactIdjbehave/artifactId -version2.1.1-SNAPSHOT/version +version2.1.1/version /parent artifactIdjbehave-maven-plugin/artifactId packagingmaven-plugin/packaging Modified: branches/jbehave-2.1.x/pom.xml (1022 => 1023) --- branches/jbehave-2.1.x/pom.xml 2009-01-24 18:57:03 UTC (rev 1022) +++ branches/jbehave-2.1.x/pom.xml 2009-01-24 19:05:25 UTC (rev 1023) @@ -3,7 +3,7 @@ groupIdorg.jbehave/groupId artifactIdjbehave/artifactId packagingpom/packaging - version2.1.1-SNAPSHOT/version + version2.1.1/version nameJBehave/name inceptionYear2003/inceptionYear description / @@ -312,9 +312,9 @@ contributors / scm -connectionscm:svn:https://svn.codehaus.org/jbehave/branches/jbehave-2.1.x/connection -developerConnectionscm:svn:https://svn.codehaus.org/jbehave/branches/jbehave-2.1.x/developerConnection -urlhttp://svn.codehaus.org/jbehave/branches/jbehave-2.1.x/url +connectionscm:svn:https://svn.codehaus.org/jbehave/tags/jbehave-2.1.1/connection +developerConnectionscm:svn:https://svn.codehaus.org/jbehave/tags/jbehave-2.1.1/developerConnection +urlhttp://svn.codehaus.org/jbehave/tags/jbehave-2.1.1/url /scm distributionManagement To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
[jbehave-scm] [1024] tags: [maven-release-plugin] copy for tag jbehave-2.1.1
Title: [1024] tags: [maven-release-plugin] copy for tag jbehave-2.1.1
Revision 1024
Author mauro
Date 2009-01-24 13:05:33 -0600 (Sat, 24 Jan 2009)
Log Message
[maven-release-plugin] copy for tag jbehave-2.1.1
Added Paths
tags/jbehave-2.1.1/
tags/jbehave-2.1.1/distribution/pom.xml
tags/jbehave-2.1.1/jbehave-ant/pom.xml
tags/jbehave-2.1.1/jbehave-core/pom.xml
tags/jbehave-2.1.1/jbehave-maven-plugin/pom.xml
tags/jbehave-2.1.1/pom.xml
Removed Paths
tags/jbehave-2.1.1/distribution/pom.xml
tags/jbehave-2.1.1/jbehave-ant/pom.xml
tags/jbehave-2.1.1/jbehave-core/pom.xml
tags/jbehave-2.1.1/jbehave-maven-plugin/pom.xml
tags/jbehave-2.1.1/pom.xml
Diff
Copied: tags/jbehave-2.1.1 (from rev 1021, branches/jbehave-2.1.x) ( => )
Deleted: tags/jbehave-2.1.1/distribution/pom.xml
===
--- branches/jbehave-2.1.x/distribution/pom.xml 2009-01-24 18:46:36 UTC (rev 1021)
+++ tags/jbehave-2.1.1/distribution/pom.xml 2009-01-24 19:05:33 UTC (rev 1024)
@@ -1,159 +0,0 @@
-project xmlns=http://maven.apache.org/POM/4.0.0 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd
- modelVersion4.0.0/modelVersion
- parent
-groupIdorg.jbehave/groupId
-artifactIdjbehave/artifactId
-version2.1.1-SNAPSHOT/version
- /parent
- artifactIdjbehave-distribution/artifactId
- packagingpom/packaging
- nameJBehave Distribution/name
- dependencies
-dependency
- groupId${pom.groupId}/groupId
- artifactIdjbehave-core/artifactId
- version${pom.version}/version
-/dependency
-dependency
- groupId${pom.groupId}/groupId
- artifactIdjbehave-maven-plugin/artifactId
- version${pom.version}/version
-/dependency
- /dependencies
- build
-plugins
- plugin
-groupIdorg.codehaus.xsite/groupId
-artifactIdxsite-maven-plugin/artifactId
-configuration
- sourceDirectoryPath${basedir}/src/site//sourceDirectoryPath
- sitemapPathcontent/sitemap.xml/sitemapPath
- skinPathtemplates/skin.html/skinPath
- resourcePathsresources/resourcePaths
- outputDirectoryPath${project.build.directory}/site/outputDirectoryPath
-/configuration
-executions
- execution
-phaseinstall/phase
-goals
- goalrun/goal
-/goals
- /execution
-/executions
- /plugin
- plugin
-groupIdorg.apache.maven.plugins/groupId
-artifactIdmaven-dependency-plugin/artifactId
-executions
- execution
-idunpack-javadoc-core/id
-phaseinstall/phase
-goals
- goalunpack/goal
-/goals
-configuration
- outputDirectory${project.build.directory}/site/javadoc/core/outputDirectory
- overWriteReleasesfalse/overWriteReleases
- overWriteSnapshotstrue/overWriteSnapshots
- artifactItems
-artifactItem
- groupId${pom.groupId}/groupId
- artifactIdjbehave-core/artifactId
- version${pom.version}/version
- classifierjavadoc/classifier
-/artifactItem
- /artifactItems
-/configuration
- /execution
- execution
-idunpack-javadoc-ant/id
-phaseinstall/phase
-goals
- goalunpack/goal
-/goals
-configuration
- outputDirectory${project.build.directory}/site/javadoc/ant/outputDirectory
- overWriteReleasesfalse/overWriteReleases
- overWriteSnapshotstrue/overWriteSnapshots
- artifactItems
-artifactItem
- groupId${pom.groupId}/groupId
- artifactIdjbehave-ant/artifactId
- version${pom.version}/version
- classifierjavadoc/classifier
-/artifactItem
- /artifactItems
-/configuration
- /execution
- execution
-idunpack-javadoc-maven-plugin/id
-phaseinstall/phase
-goals
- goalunpack/goal
-/goals
-configuration
- outputDirectory${project.build.directory}/site/javadoc/maven-plugin/outputDirectory
- overWriteReleasesfalse/overWriteReleases
- overWriteSnapshotstrue/overWriteSnapshots
- artifactItems
-artifactItem
- groupId${pom.groupId}/groupId
- artifactIdjbehave-maven-plugin/artifactId
- version${pom.version}/version
- classifierjavadoc/classifier
-/artifactItem
- /artifactItems
-/configuration
- /execution
-/executions
- /plugin
-
[jbehave-dev] [jira] Updated: (JBEHAVE-155) Maven plugin can't identify Scenario classes in src/test/java
[
http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-155:
-
Fix Version/s: 2.2
Fixed in 2.1.1 and trunk.
Maven plugin can't identify Scenario classes in src/test/java
-
Key: JBEHAVE-155
URL: http://jira.codehaus.org/browse/JBEHAVE-155
Project: JBehave
Issue Type: Bug
Components: Maven Plugin
Affects Versions: 2.1
Environment: Maven 2.0.9, Java 1.5.0_16
Reporter: Binil Thomas
Assignee: Mauro Talevi
Fix For: 2.1.1, 2.2
Attachments: jbehave-bug-report.tar.gz
I have the JBehave Maven plugin configured with test scope. In 2.0.1, the
plugin was able to pick up the Scenario classes from src/test/java, but in
2.1 it fails to. Please try running the attached maven project with different
-Djbehave.version settings to reproduce the error.
$ mvn -Djbehave.version=2.0.1 clean integration-test
...
[INFO] [jbehave:run-scenarios {execution: run-scenarios-listed}]
[INFO] Running scenario binil.scenarios.MyScenario
...
$ mvn -Djbehave.version=2.1 clean integration-test
...
[INFO] [jbehave:run-scenarios {execution: run-scenarios-listed}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to instantiate scenario 'binil.scenarios.MyScenario'
Embedded error: The scenario 'binil.scenarios.MyScenario' could not be
instantiated with class loader: [org.jbehave.scenario.ScenarioClassLoader
urls=[/Users/binil/work/jbehave-bug-report/target/classes]]
--
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
[jbehave-dev] [jira] Resolved: (JBEHAVE-155) Maven plugin can't identify Scenario classes in src/test/java
[
http://jira.codehaus.org/browse/JBEHAVE-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-155.
--
Resolution: Fixed
Version 2.1.1 released.
Maven plugin can't identify Scenario classes in src/test/java
-
Key: JBEHAVE-155
URL: http://jira.codehaus.org/browse/JBEHAVE-155
Project: JBehave
Issue Type: Bug
Components: Maven Plugin
Affects Versions: 2.1
Environment: Maven 2.0.9, Java 1.5.0_16
Reporter: Binil Thomas
Assignee: Mauro Talevi
Fix For: 2.1.1, 2.2
Attachments: jbehave-bug-report.tar.gz
I have the JBehave Maven plugin configured with test scope. In 2.0.1, the
plugin was able to pick up the Scenario classes from src/test/java, but in
2.1 it fails to. Please try running the attached maven project with different
-Djbehave.version settings to reproduce the error.
$ mvn -Djbehave.version=2.0.1 clean integration-test
...
[INFO] [jbehave:run-scenarios {execution: run-scenarios-listed}]
[INFO] Running scenario binil.scenarios.MyScenario
...
$ mvn -Djbehave.version=2.1 clean integration-test
...
[INFO] [jbehave:run-scenarios {execution: run-scenarios-listed}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to instantiate scenario 'binil.scenarios.MyScenario'
Embedded error: The scenario 'binil.scenarios.MyScenario' could not be
instantiated with class loader: [org.jbehave.scenario.ScenarioClassLoader
urls=[/Users/binil/work/jbehave-bug-report/target/classes]]
--
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
[jbehave-dev] JBehave 2.1.1 released
JBehave 2.1.1 has been released with following changelog: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10680fixfor=14933 Releases available from http://jbehave.org/software/download Cheers - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
