[jbehave-dev] [jira] Resolved: (JBEHAVE-484) Upgrade to latest released version of build plugins
[ http://jira.codehaus.org/browse/JBEHAVE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-484. -- Resolution: Fixed > Upgrade to latest released version of build plugins > --- > > Key: JBEHAVE-484 > URL: http://jira.codehaus.org/browse/JBEHAVE-484 > Project: JBehave > Issue Type: Task > Components: Build >Reporter: Mauro Talevi >Assignee: Mauro Talevi >Priority: Minor > Fix For: 3.4 > > -- 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] Created: (JBEHAVE-484) Upgrade to latest released version of build plugins
Upgrade to latest released version of build plugins --- Key: JBEHAVE-484 URL: http://jira.codehaus.org/browse/JBEHAVE-484 Project: JBehave Issue Type: Task Components: Build Reporter: Mauro Talevi Assignee: Mauro Talevi Priority: Minor Fix For: 3.4 -- 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.3.2-26-g1c12ccc
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 1c12bd29dc7cf864d346b2cbd9cfd54cbf12 (commit) from 7cc737233527d3c53343b54efb285c25691c0d51 (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 1c12bd29dc7cf864d346b2cbd9cfd54cbf12 Author: Mauro Talevi Date: Sat Apr 16 15:56:33 2011 +0200 JBEHAVE-484: Upgraded plugin versions to latest releases available. Fixed default value in EmbedderMojo, only relevant to unit test. --- Summary of changes: .../org/jbehave/mojo/AbstractEmbedderMojo.java |2 +- .../org/jbehave/mojo/EmbedderMojoBehaviour.java|4 +- pom.xml| 31 +++ 3 files changed, 15 insertions(+), 22 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, jbehave-3.3.x, updated. jbehave-3.3.2-27-g5c034fd
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, jbehave-3.3.x has been updated via 5c034fd4b13e7efe5a47ba58ae2f86980dd6498f (commit) from 1a9addaf9a567c8cb953bf5ee2ed962d71b0 (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 5c034fd4b13e7efe5a47ba58ae2f86980dd6498f Author: Mauro Talevi Date: Sat Apr 16 12:13:51 2011 +0200 Removed archetypes and jbehave-odf from 3.3.x branch. --- Summary of changes: archetypes/jbehave-groovy-archetype/pom.xml| 15 --- .../META-INF/maven/archetype-metadata.xml | 28 -- .../src/main/resources/archetype-resources/pom.xml | 103 .../groovy/configuration/MyReporterBuilder.groovy | 12 --- .../src/main/groovy/steps/MySteps.groovy | 32 -- .../src/main/java/GroovyStories.java | 45 - .../src/main/resources/stories/my.story|8 -- archetypes/jbehave-simple-archetype/pom.xml| 15 --- .../META-INF/maven/archetype-metadata.xml | 25 - .../src/main/resources/archetype-resources/pom.xml | 99 --- .../src/main/java/MyStories.java | 82 .../src/main/java/steps/MySteps.java | 13 --- .../src/main/resources/stories/my.story| 10 -- archetypes/jbehave-spring-archetype/pom.xml| 15 --- .../META-INF/maven/archetype-metadata.xml | 25 - .../src/main/resources/archetype-resources/pom.xml | 99 --- .../src/main/java/MyStories.java | 89 - .../src/main/java/steps/MySteps.java | 13 --- .../src/main/resources/my_steps.xml|9 -- .../src/main/resources/stories/my.story| 10 -- archetypes/pom.xml | 77 --- distribution/pom.xml | 25 - distribution/src/site/content/code-coverage.html |2 - distribution/src/site/content/dependencies.html|1 - distribution/src/site/content/javadoc.html |2 - .../src/site/content/locating-stories.html | 18 jbehave-odf/pom.xml| 26 - .../jbehave/core/io/odf/LoadOdtFromClasspath.java | 31 -- .../org/jbehave/core/io/odf/LoadOdtFromURL.java| 22 .../java/org/jbehave/core/io/odf/OdfUtils.java | 59 --- .../jbehave/core/io/odf/OdtLoaderBehaviour.java| 61 .../org/jbehave/core/io/odf/stories/a_story.odt| Bin 10387 -> 0 bytes .../org/jbehave/core/io/odf/stories/a_story.txt| 27 - pom.xml|2 - 34 files changed, 0 insertions(+), 1100 deletions(-) delete mode 100644 archetypes/jbehave-groovy-archetype/pom.xml delete mode 100644 archetypes/jbehave-groovy-archetype/src/main/resources/META-INF/maven/archetype-metadata.xml delete mode 100644 archetypes/jbehave-groovy-archetype/src/main/resources/archetype-resources/pom.xml delete mode 100644 archetypes/jbehave-groovy-archetype/src/main/resources/archetype-resources/src/main/groovy/configuration/MyReporterBuilder.groovy delete mode 100644 archetypes/jbehave-groovy-archetype/src/main/resources/archetype-resources/src/main/groovy/steps/MySteps.groovy delete mode 100644 archetypes/jbehave-groovy-archetype/src/main/resources/archetype-resources/src/main/java/GroovyStories.java delete mode 100644 archetypes/jbehave-groovy-archetype/src/main/resources/archetype-resources/src/main/resources/stories/my.story delete mode 100644 archetypes/jbehave-simple-archetype/pom.xml delete mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/META-INF/maven/archetype-metadata.xml delete mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/archetype-resources/pom.xml delete mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/archetype-resources/src/main/java/MyStories.java delete mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/archetype-resources/src/main/java/steps/MySteps.java delete mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/archetype-resources/src/main/resources/stories/my.story delete mode 100644 archetypes/jbehave-spring-archetype/pom.xml delete mode 100644 archetypes/jbehave-spring-archetype/src/main/resources/META-INF/maven/archetype-metadata.xml delete mode 100644 archetypes/jbehave-spring-archetype/src/main/resources/archetype-resources/pom.xml delete mode 100644 archetypes/jbehave-spring-archetype/src/
[jbehave-scm] jbehave-core branch, jbehave-3.3.x, created. jbehave-3.3.2-26-g1a9add5
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, jbehave-3.3.x has been created at 1a9addaf9a567c8cb953bf5ee2ed962d71b0 (commit) - Log - commit 1a9addaf9a567c8cb953bf5ee2ed962d71b0 Author: Mauro Talevi Date: Sat Apr 16 12:03:55 2011 +0200 Changed branch version to 3.3.x-SNAPSHOT. --- 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-472) Improve state management of StoryRunner
[ http://jira.codehaus.org/browse/JBEHAVE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-472. -- Resolution: Fixed > Improve state management of StoryRunner > --- > > Key: JBEHAVE-472 > URL: http://jira.codehaus.org/browse/JBEHAVE-472 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.3 >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.4 > > > We need to improve the state management of the StoryRunner. > Currently after every set of steps run the state is reset and the scenario > @Before/@After steps are run separately from the normal steps, causing wierd > behaviours when there are failure in the @Before steps but not in the normal > steps. Examples of such a behaviour are the trader > failing_before_after.story and failing_before_stories.story. > A better and more intuitive state management should be in place, keeping > state in the run context. The state should be reset by default before each > scenario (to ensure backward compat) but will be shared between the > @Before/@After steps and the normal steps. > We should also have the option to not reset it before each scenario to allow > for failures in the @BeforeStory/Stories steps to propagate to the scenario > steps in the same run context. > Once a failing state in a given run context, the steps that follow will not > be performed, as customary with normal steps. -- 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-476) Archetypes to boostrap creation of projects
[ http://jira.codehaus.org/browse/JBEHAVE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-476: - Component/s: Archetypes > Archetypes to boostrap creation of projects > --- > > Key: JBEHAVE-476 > URL: http://jira.codehaus.org/browse/JBEHAVE-476 > Project: JBehave > Issue Type: New Feature > Components: Archetypes >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.4 > > > Archetypes are a useful way to help projects bootstrap their testing setup. > Maven natively supports the concept of archetypes, which are templates used > to generate new projects. > The archetype resources are Velocity templates packaged as a jar. > Maven provides a META-INF/maven/archetype-descriptor.xml, but other tools can > still use the archetype resources. -- 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-472) Improve state management of StoryRunner
[ http://jira.codehaus.org/browse/JBEHAVE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-472: - Description: We need to improve the state management of the StoryRunner. Currently after every set of steps run the state is reset and the scenario @Before/@After steps are run separately from the normal steps, causing wierd behaviours when there are failure in the @Before steps but not in the normal steps. Examples of such a behaviour are the trader failing_before_after.story and failing_before_stories.story. A better and more intuitive state management should be in place, keeping state in the run context. The state should be reset by default before each scenario (to ensure backward compat) but will be shared between the @Before/@After steps and the normal steps. We should also have the option to not reset it before each scenario to allow for failures in the @BeforeStory/Stories steps to propagate to the scenario steps in the same run context. Once a failing state in a given run context, the steps that follow will not be performed, as customary with normal steps. was: We need to improve the state management of the StoryRunner. Currently after every set of steps run the state is reset and the scenario @Before/@After steps are run separately from the normal steps, causing wierd/wrong behaviours when there are failure in the @Before steps but not in the normal steps. An example of such a behaviour is the trader failing_before_after.story. If we use the storyFailure to drive the state it causes other behaviour to break. A better and more intuitive state management should be kept at scenario level. We should instead hold a reference to a scenarioFailure which can be reset before each scenario but will be shared between the @Before/@After steps and the normal scenario steps. > Improve state management of StoryRunner > --- > > Key: JBEHAVE-472 > URL: http://jira.codehaus.org/browse/JBEHAVE-472 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.3 >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.4 > > > We need to improve the state management of the StoryRunner. > Currently after every set of steps run the state is reset and the scenario > @Before/@After steps are run separately from the normal steps, causing wierd > behaviours when there are failure in the @Before steps but not in the normal > steps. Examples of such a behaviour are the trader > failing_before_after.story and failing_before_stories.story. > A better and more intuitive state management should be in place, keeping > state in the run context. The state should be reset by default before each > scenario (to ensure backward compat) but will be shared between the > @Before/@After steps and the normal steps. > We should also have the option to not reset it before each scenario to allow > for failures in the @BeforeStory/Stories steps to propagate to the scenario > steps in the same run context. > Once a failing state in a given run context, the steps that follow will not > be performed, as customary with normal steps. -- 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
