[jbehave-dev] [jira] Created: (JBEHAVE-348) SpringStepsFactory should not try to instantiate abstract beans
SpringStepsFactory should not try to instantiate abstract beans Key: JBEHAVE-348 URL: http://jira.codehaus.org/browse/JBEHAVE-348 Project: JBehave Issue Type: Improvement Components: Spring Support Affects Versions: 3.0 Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.0.1 Spring allows the declaration of abstract beans. These should be identified via their bean type and not instantiated. -- 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] jbehave-core branch, master, updated. jbehave-3.0-9-g8c06cd3
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The branch, master has been updated via 8c06cd3f2d315b2097c8c70a2016fab3f7d15688 (commit) from 84266956b7662894667a1e44a742a8c7e5ee9c73 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 8c06cd3f2d315b2097c8c70a2016fab3f7d15688 Author: Mauro Talevi Date: Fri Sep 24 13:05:48 2010 +0200 JBEHAVE-348: Prevent Spring abstract beans from being instantiated. --- Summary of changes: .../org/jbehave/examples/trader/spring/steps.xml |3 +++ .../examples/trader/steps/AbstractSteps.java | 12 .../core/steps/spring/SpringStepsFactory.java | 11 --- .../steps/spring/SpringStepsFactoryBehaviour.java |4 .../java/org/jbehave/core/steps/spring/steps.xml |3 +++ 5 files changed, 30 insertions(+), 3 deletions(-) create mode 100644 examples/trader/src/main/java/org/jbehave/examples/trader/steps/AbstractSteps.java hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-348) SpringStepsFactory should not try to instantiate abstract beans
[ http://jira.codehaus.org/browse/JBEHAVE-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-348. -- Resolution: Fixed > SpringStepsFactory should not try to instantiate abstract beans > > > Key: JBEHAVE-348 > URL: http://jira.codehaus.org/browse/JBEHAVE-348 > Project: JBehave > Issue Type: Improvement > Components: Spring Support >Affects Versions: 3.0 >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.0.1 > > > Spring allows the declaration of abstract beans. These should be identified > via their bean type and not instantiated. -- 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-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: (was: 3.0.1) 3.0.2 > HTML report numbers could be more tabular > -- > > Key: JBEHAVE-339 > URL: http://jira.codehaus.org/browse/JBEHAVE-339 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.0 >Reporter: Paul Hammant >Assignee: Mauro Talevi > Fix For: 3.0.2 > > > guice.stories.simple_guice_exampleScenarios: 1 (Failed: 0) Steps: 3 > (Successful: 3; Pending: 0; Not Performed: 0; Failed: 0; Ignorable: 0) > i18n.stories.fr_trader_is_alerted_of_status Scenarios: 1 (Failed: 0) Steps: > 13 (Successful: 0; Pending: 4; Not Performed: 9; Failed: 0; Ignorable: 0) > i18n.stories.it_trader_is_alerted_of_status Scenarios: 2 (Failed: 0) Steps: > 15 (Successful: 7; Pending: 8; Not Performed: 0; Failed: 0; Ignorable: 0) > The output formats as a string. There are some numbers is parens. These > should really be numbers > There should also be totals at the bottom of the set, and column headings at > the top :) -- 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] jbehave-core branch, master, updated. jbehave-3.0-10-g7e313bd
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The branch, master has been updated via 7e313bddf170d0d9fcb14152608ca4fd76ccef1d (commit) from 8c06cd3f2d315b2097c8c70a2016fab3f7d15688 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 7e313bddf170d0d9fcb14152608ca4fd76ccef1d Author: Mauro Talevi Date: Fri Sep 24 13:09:17 2010 +0200 Updated release notes. --- Summary of changes: distribution/src/site/content/release-notes.html | 22 ++ 1 files changed, 22 insertions(+), 0 deletions(-) hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.0-11-g71006aa
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The branch, master has been updated via 71006aa5f41fd174dd45f361e69f852e6e95b10c (commit) from 7e313bddf170d0d9fcb14152608ca4fd76ccef1d (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 71006aa5f41fd174dd45f361e69f852e6e95b10c Author: Mauro Talevi Date: Fri Sep 24 13:19:49 2010 +0200 [maven-release-plugin] prepare release jbehave-3.0.1 --- Summary of changes: distribution/pom.xml |2 +- jbehave-ant/pom.xml |2 +- jbehave-core/pom.xml |2 +- jbehave-guice/pom.xml|2 +- jbehave-maven-plugin/pom.xml |2 +- jbehave-pico/pom.xml |2 +- jbehave-spring/pom.xml |2 +- pom.xml |2 +- 8 files changed, 8 insertions(+), 8 deletions(-) hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core annotated tag, jbehave-3.0.1, created. jbehave-3.0.1
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The annotated tag, jbehave-3.0.1 has been created at 2d8567d06894299f1101ff5123e3f5a40c54db81 (tag) tagging 71006aa5f41fd174dd45f361e69f852e6e95b10c (commit) replaces jbehave-3.0 tagged by Mauro Talevi on Fri Sep 24 13:19:55 2010 +0200 - Log - [maven-release-plugin] copy for tag jbehave-3.0.1 Mauro Talevi (11): [maven-release-plugin] prepare for next development iteration Updated examples to use latest snapshot. Fixed error in regex patterns, as spotted by Ronald Harring on user list. Removed directory erroneously added to scm. JBEHAVE-344: Failures in before and after methods now are reportable. JBEHAVE-342: Added @requiresDependencyResolution annotation, as required by Maven 3. Change is Maven 2 compatible. JBEHAVE-346: Added getter/setter for FilePathResolver JBEHAVE-347: Ensure all use methods in Configuration return self. JBEHAVE-348: Prevent Spring abstract beans from being instantiated. Updated release notes. [maven-release-plugin] prepare release jbehave-3.0.1 --- hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.0.1-1-gdedc440
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The branch, master has been updated via dedc4401921e76a3458205b3b286935a772d7564 (commit) from 71006aa5f41fd174dd45f361e69f852e6e95b10c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit dedc4401921e76a3458205b3b286935a772d7564 Author: Mauro Talevi Date: Fri Sep 24 13:20:00 2010 +0200 [maven-release-plugin] prepare for next development iteration --- Summary of changes: distribution/pom.xml |2 +- jbehave-ant/pom.xml |2 +- jbehave-core/pom.xml |2 +- jbehave-guice/pom.xml|2 +- jbehave-maven-plugin/pom.xml |2 +- jbehave-pico/pom.xml |2 +- jbehave-spring/pom.xml |2 +- pom.xml |2 +- 8 files changed, 8 insertions(+), 8 deletions(-) hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.0-10-gc5b7094
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-web". The branch, master has been updated via c5b709407c4d0af912c76e4c1da11eb529cae25d (commit) from c2aecc22fc6a9fd4e571fdff89fd1a76900ba84f (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit c5b709407c4d0af912c76e4c1da11eb529cae25d Author: Paul Hammant Date: Fri Sep 24 08:21:26 2010 -0500 JBEHAVE-345: overridable WebDriver instantiation --- Summary of changes: .../FailingScenarioScreenshotCapture.java |6 +- .../trader/webdriver/TraderWebStories.java |5 +- .../web/selenium/PerScenarioWebDriverSteps.java| 31 .../web/selenium/PerStoriesWebDriverSteps.java | 32 .../web/selenium/PerStoryWebDriverSteps.java | 33 - .../web/selenium/WebDriverConfiguration.java | 39 -- .../org/jbehave/web/selenium/WebDriverContext.java | 15 .../org/jbehave/web/selenium/WebDriverPage.java| 13 .../org/jbehave/web/selenium/WebDriverProxy.java | 69 -- .../jbehave/web/selenium/WebDriverStepMonitor.java | 66 - .../org/jbehave/web/selenium/WebDriverSteps.java | 20 - .../selenium/PerScenarioWebDriverStepsTest.java| 76 .../web/selenium/PerStoryWebDriverStepsTest.java | 75 --- .../web/selenium/WebDriverConfigurationTest.java | 56 -- .../web/webdriver/PerScenarioWebDriverSteps.java | 11 +-- .../web/webdriver/PerStoriesWebDriverSteps.java|9 +-- .../web/webdriver/PerStoryWebDriverSteps.java | 10 +-- .../web/webdriver/WebDriverConfiguration.java |6 +- .../org/jbehave/web/webdriver/WebDriverProxy.java | 14 +++- .../org/jbehave/web/webdriver/WebDriverSteps.java | 13 ++-- .../webdriver/PerScenarioWebDriverStepsTest.java | 12 ++-- .../web/webdriver/PerStoryWebDriverStepsTest.java | 11 ++-- 22 files changed, 44 insertions(+), 578 deletions(-) delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/PerScenarioWebDriverSteps.java delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/PerStoriesWebDriverSteps.java delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/PerStoryWebDriverSteps.java delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/WebDriverConfiguration.java delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/WebDriverContext.java delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/WebDriverPage.java delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/WebDriverProxy.java delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/WebDriverStepMonitor.java delete mode 100644 web-selenium/src/main/java/org/jbehave/web/selenium/WebDriverSteps.java delete mode 100644 web-selenium/src/test/java/org/jbehave/web/selenium/PerScenarioWebDriverStepsTest.java delete mode 100644 web-selenium/src/test/java/org/jbehave/web/selenium/PerStoryWebDriverStepsTest.java delete mode 100644 web-selenium/src/test/java/org/jbehave/web/selenium/WebDriverConfigurationTest.java hooks/post-receive -- jbehave-web To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.0-11-g4c45639
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-web". The branch, master has been updated via 4c45639889e161fd9a5b0b0fb5d6dc077a2a7a9c (commit) from c5b709407c4d0af912c76e4c1da11eb529cae25d (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 4c45639889e161fd9a5b0b0fb5d6dc077a2a7a9c Author: Paul Hammant Date: Fri Sep 24 08:30:46 2010 -0500 JBEHAVE-345: place marker for future WebDriver functionality --- Summary of changes: .../web/webdriver/WebDriverStepMonitor.java|3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) hooks/post-receive -- jbehave-web To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.0-12-gb58eb1c
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-web". The branch, master has been updated via b58eb1cd293a00e8f2b3054237d210db3bb4a0e1 (commit) from 4c45639889e161fd9a5b0b0fb5d6dc077a2a7a9c (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit b58eb1cd293a00e8f2b3054237d210db3bb4a0e1 Author: Paul Hammant Date: Fri Sep 24 08:47:08 2010 -0500 JBEHAVE-345: tests working again --- Summary of changes: .../webdriver/PerScenarioWebDriverStepsTest.java |3 +-- .../web/webdriver/PerStoryWebDriverStepsTest.java |4 +--- 2 files changed, 2 insertions(+), 5 deletions(-) hooks/post-receive -- jbehave-web To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Resolved: (JBEHAVE-139) Convert ant build to use ivy for dependencies
[ http://jira.codehaus.org/browse/JBEHAVE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-139. -- Resolution: Won't Fix > Convert ant build to use ivy for dependencies > - > > Key: JBEHAVE-139 > URL: http://jira.codehaus.org/browse/JBEHAVE-139 > Project: JBehave > Issue Type: Improvement > Components: Build >Affects Versions: 2.0 > Environment: Any >Reporter: Dan North >Assignee: Dan North > > We currently have a lib directory with various subdirectories containing a > number of dependent jars. As we add more adapters (spring, pico, test-ng) > this is going to get more complex. > Ivy (http://ant.apache.org/ivy) has a similar dependency resolution model to > maven. By migrating to ivy we can simplify the build and remove the dependent > third-party jars from the repository. -- 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-115) Undoable steps
[ http://jira.codehaus.org/browse/JBEHAVE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-115. -- Resolution: Duplicate Resolving as duplicate of JBEHAVE-129, until someone comes up with a more elaborate use case. > Undoable steps > -- > > Key: JBEHAVE-115 > URL: http://jira.codehaus.org/browse/JBEHAVE-115 > Project: JBehave > Issue Type: New Feature >Reporter: Elizabeth Keogh > > Sometimes when we set up a context or cause an event to happen, it's nice to > clean up any changes so that we don't affect other tests running. > No idea how to make the undoable work, but doesn't stop me wanting it! -- 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] Commented: (JBEHAVE-146) PendingErrorStrategy choices needs one more.
[
http://jira.codehaus.org/browse/JBEHAVE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236361#action_236361
]
Mauro Talevi commented on JBEHAVE-146:
--
Paul, do you feel you still need more choices?
> PendingErrorStrategy choices needs one more.
>
>
> Key: JBEHAVE-146
> URL: http://jira.codehaus.org/browse/JBEHAVE-146
> Project: JBehave
> Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Paul Hammant
>
> PASSING and SILENT are identical method bodies
> The same is true of FAILING and RETHROW
> [ moving past that issue ]
> Could y'all make one more strategy ?
> {noformat}
>/**
> * This will continue the scenario as PASSING would, but at the end,
> remember that there was an issue during the run, and throw it again then.
> */
> PendingErrorStrategy FAIL_LATER = new PendingErrorStrategy() {
> public void handleError(Throwable throwable) {
> // ??
> }
> };
> {noformat}
> Note, I've even given you some /** Javadoc */ for this, as
> http://jbehave.org/javadoc/latest/core/org/jbehave/scenario/errors/PendingErrorStrategy.html
> is a little sparse on information ;-)
--
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] Commented: (JBEHAVE-146) PendingErrorStrategy choices needs one more.
[
http://jira.codehaus.org/browse/JBEHAVE-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236362#action_236362
]
Mauro Talevi commented on JBEHAVE-146:
--
Paul, do you feel you still need more choices?
> PendingErrorStrategy choices needs one more.
>
>
> Key: JBEHAVE-146
> URL: http://jira.codehaus.org/browse/JBEHAVE-146
> Project: JBehave
> Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Paul Hammant
>
> PASSING and SILENT are identical method bodies
> The same is true of FAILING and RETHROW
> [ moving past that issue ]
> Could y'all make one more strategy ?
> {noformat}
>/**
> * This will continue the scenario as PASSING would, but at the end,
> remember that there was an issue during the run, and throw it again then.
> */
> PendingErrorStrategy FAIL_LATER = new PendingErrorStrategy() {
> public void handleError(Throwable throwable) {
> // ??
> }
> };
> {noformat}
> Note, I've even given you some /** Javadoc */ for this, as
> http://jbehave.org/javadoc/latest/core/org/jbehave/scenario/errors/PendingErrorStrategy.html
> is a little sparse on information ;-)
--
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-153) I would like to add priority to my scenarios
[ http://jira.codehaus.org/browse/JBEHAVE-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-153: - Component/s: Core Description: I would like to be able to add priority to my textual scenarios and should be available to the StoryReporter. This priority is used to tell in what order the different scenarios should be implemented. E.g. if (in StoryReporter) public void beforeScenario(String title); is changed to public void beforeScenario(String title, int priority); The priority can be used to create a visual report (e.g. in HTML). The priority can also be used to raise warnings if a high priority scenario is pending, while there is activity on scenarios with less priority. was: I would like to be able to add priority to my textual scenarios and should be available to the ScenarioReporter. This priority is used to tell in what order the different scenarios should be implemented. E.g. if (in ScnearioReporter) public void beforeScenario(String title); is changed to public void beforeScenario(String title, int priority); The priority can be used to create a visual report (e.g. in HTML). The priority can also be used to raise warnings if a high priority scenario is pending, while there is activity on scenarios with less priority. Set component to core. This use case will probably be addressed by JBEHAVE-220. > I would like to add priority to my scenarios > > > Key: JBEHAVE-153 > URL: http://jira.codehaus.org/browse/JBEHAVE-153 > Project: JBehave > Issue Type: New Feature > Components: Core >Reporter: Egil Østhus >Priority: Minor > > I would like to be able to add priority to my textual scenarios and should be > available to the StoryReporter. This priority is used to tell in what order > the different scenarios should be implemented. > E.g. if (in StoryReporter) > public void beforeScenario(String title); > is changed to > public void beforeScenario(String title, int priority); > The priority can be used to create a visual report (e.g. in HTML). > The priority can also be used to raise warnings if a high priority scenario > is pending, while there is activity on scenarios with less priority. -- 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-193) Cannot find the persistence.xml file
[
http://jira.codehaus.org/browse/JBEHAVE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-193.
--
Resolution: Cannot Reproduce
Closing as cannot be reproduced. Please re-open if you can provide a
re-produceable example.
> Cannot find the persistence.xml file
>
>
> Key: JBEHAVE-193
> URL: http://jira.codehaus.org/browse/JBEHAVE-193
> Project: JBehave
> Issue Type: Bug
> Components: Maven Plugin
>Affects Versions: 2.3
> Environment: intellij and ubuntu command line
>Reporter: Jim Barrows
>Assignee: Mauro Talevi
>
> Running the sceanario from either eclipse or intellij, the
> Persistence.createEntityManagerFactory("party-test"); finds the
> persistence.xml file just fine, and everything works. However running it via
> the maven plugin, and it can't find the file at all. I suspect this is a
> classpath issue, since the persistence.xml file is in a /META-INF directory
> and not in the normal classpath. I could be wrong though.
--
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-260) Improve SpringStepsFactory to allow delegating the CandidateStep creation to other factories
[
http://jira.codehaus.org/browse/JBEHAVE-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-260.
--
Resolution: Fixed
Fix Version/s: 3.0.2
SpringStepsFactory provides protected method:
{code}
protected List stepsInstances();
{code}
> Improve SpringStepsFactory to allow delegating the CandidateStep creation to
> other factories
>
>
> Key: JBEHAVE-260
> URL: http://jira.codehaus.org/browse/JBEHAVE-260
> Project: JBehave
> Issue Type: Improvement
> Components: Core
>Affects Versions: 2.5.1
>Reporter: Bruno Bieth
> Fix For: 3.0.2
>
>
> Change the SpringStepsFactory so it doesn't create CandidateSteps but rather
> return bean instances. That way I can have a different way of instanciating
> CandidateSteps.
> {code}
> addSteps(new ParameterConverterStepsFactory().createCandidateSteps( new
> SpringStepsFactory(context).createStepsInstances() ));
> {code}
> And the simplified SpringStepsFactory :
> {code}
> public class SpringStepsFactory {
> private final ListableBeanFactory parent;
>
> public SpringStepsFactory(ListableBeanFactory parent) {
> this.parent = parent;
> }
> public Object[] createStepsInstances() {
> List steps = new ArrayList();
> for (String name : parent.getBeanDefinitionNames()) {
> Object bean = parent.getBean(name);
> if (containsScenarioAnnotations(bean.getClass())) {
> steps.add(bean);
> }
> }
> return steps.toArray(new Object[steps.size()]);
> }
>
> private boolean containsScenarioAnnotations(Class componentClass) {
> for (Method method : componentClass.getMethods()) {
> for (Annotation annotation : method.getAnnotations()) {
> if
> (annotation.annotationType().getName().startsWith("org.jbehave.scenario.annotations"))
> {
> return true;
> }
> }
> }
> return false;
> }
> }
> {code}
--
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] jbehave-web branch, master, updated. jbehave-web-3.0-13-gf69d758
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-web". The branch, master has been updated via f69d7582048a455c805b25dfa4457ccb5407a179 (commit) from b58eb1cd293a00e8f2b3054237d210db3bb4a0e1 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit f69d7582048a455c805b25dfa4457ccb5407a179 Author: Paul Hammant Date: Fri Sep 24 09:57:37 2010 -0500 JBEHAVE-345: move to factory design as per Simon's design --- Summary of changes: .../FailingScenarioScreenshotCapture.java |6 +- .../trader/webdriver/TraderWebStories.java | 13 ++-- .../examples/trader/webdriver/pages/FindSteps.java |4 +- .../web/examples/trader/webdriver/pages/Home.java |6 +- .../trader/webdriver/pages/PageFactory.java| 14 ++-- .../examples/trader/webdriver/pages/RunStory.java |6 +- .../trader/webdriver/pages/TraderPage.java |4 +- .../web/webdriver/FirefoxWebDriverFactory.java | 10 +++ .../web/webdriver/PerScenarioWebDriverSteps.java |8 +- .../web/webdriver/PerStoriesWebDriverSteps.java|8 +- .../web/webdriver/PerStoryWebDriverSteps.java | 10 ++-- .../web/webdriver/WebDriverConfiguration.java | 16 ++--- .../jbehave/web/webdriver/WebDriverFactory.java| 19 + .../web/webdriver/WebDriverFactoryImpl.java| 17 + .../org/jbehave/web/webdriver/WebDriverPage.java | 32 .../org/jbehave/web/webdriver/WebDriverProxy.java | 75 .../web/webdriver/WebDriverStepMonitor.java|9 +-- .../org/jbehave/web/webdriver/WebDriverSteps.java | 12 ++-- .../webdriver/PerScenarioWebDriverStepsTest.java | 10 ++-- .../web/webdriver/PerStoryWebDriverStepsTest.java |9 ++- .../web/webdriver/WebDriverConfigurationTest.java |5 +- 21 files changed, 128 insertions(+), 165 deletions(-) create mode 100644 web-webdriver/src/main/java/org/jbehave/web/webdriver/FirefoxWebDriverFactory.java create mode 100644 web-webdriver/src/main/java/org/jbehave/web/webdriver/WebDriverFactory.java create mode 100644 web-webdriver/src/main/java/org/jbehave/web/webdriver/WebDriverFactoryImpl.java delete mode 100644 web-webdriver/src/main/java/org/jbehave/web/webdriver/WebDriverProxy.java hooks/post-receive -- jbehave-web To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-349) JBehave Spring doesn't work with abstract beans
JBehave Spring doesn't work with abstract beans --- Key: JBEHAVE-349 URL: http://jira.codehaus.org/browse/JBEHAVE-349 Project: JBehave Issue Type: Bug Components: Spring Support Affects Versions: 3.0.1 Reporter: Tom Marsh Priority: Critical Attachments: [tmarsh]_Fixing_abstract_bean_error.patch If you use abstract beans the annotation processor blows up. I've included a patch. Its basically a try catch around the getBean step. Test data enhanced to recreate problem. -- 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-349) JBehave Spring doesn't work with abstract beans
[ http://jira.codehaus.org/browse/JBEHAVE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-349: - Fix Version/s: 3.0.2 Assignee: Mauro Talevi It's not simply the abstract class bean that it complains about, those are cared for in the isNotAbstract() method (since 3.0.1), which assumes that the context is able to determine the type of the bean. This is not always the case. In any case, a more generic solution is to wrap the bean instantiation to catch the BeansException as you suggest. > JBehave Spring doesn't work with abstract beans > --- > > Key: JBEHAVE-349 > URL: http://jira.codehaus.org/browse/JBEHAVE-349 > Project: JBehave > Issue Type: Bug > Components: Spring Support >Affects Versions: 3.0.1 >Reporter: Tom Marsh >Assignee: Mauro Talevi >Priority: Critical > Fix For: 3.0.2 > > Attachments: [tmarsh]_Fixing_abstract_bean_error.patch > > > If you use abstract beans the annotation processor blows up. > I've included a patch. Its basically a try catch around the getBean step. > Test data enhanced to recreate problem. -- 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
