[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.3.2-5-g121974a
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 121974a35c6382efaba3b1dc374cbf3aa1bc0e0d (commit)
via 9165dc49a57496d7bf822b670349192e1f31de30 (commit)
from 6da7c41cba4efd9f0139a815f60332857087bd0a (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 121974a35c6382efaba3b1dc374cbf3aa1bc0e0d
Author: Mauro Talevi
Date: Wed Apr 13 22:08:34 2011 +0200
JBEHAVE-476: Use relative resource paths in archetype pom.xml.
commit 9165dc49a57496d7bf822b670349192e1f31de30
Author: Mauro Talevi
Date: Wed Apr 13 20:36:52 2011 +0100
JBEHAVE-476: Added archetype using Spring to compose steps.
---
Summary of changes:
archetypes/jbehave-simple-archetype/pom.xml|2 +-
.../src/main/resources/archetype-resources/pom.xml |4 +-
.../pom.xml|6 ++--
.../META-INF/maven/archetype-metadata.xml |0
.../src/main/resources/archetype-resources/pom.xml |6 ++--
.../src/main/java/MyStories.java | 11 ++-
.../src/main/java/steps/MySteps.java |0
.../src/main/resources/my_steps.xml|3 +-
.../src/main/resources/stories/my.story|0
archetypes/pom.xml | 29
10 files changed, 48 insertions(+), 13 deletions(-)
copy archetypes/{jbehave-simple-archetype => jbehave-spring-archetype}/pom.xml
(68%)
copy archetypes/{jbehave-simple-archetype =>
jbehave-spring-archetype}/src/main/resources/META-INF/maven/archetype-metadata.xml
(100%)
copy archetypes/{jbehave-simple-archetype =>
jbehave-spring-archetype}/src/main/resources/archetype-resources/pom.xml (91%)
copy archetypes/{jbehave-simple-archetype =>
jbehave-spring-archetype}/src/main/resources/archetype-resources/src/main/java/MyStories.java
(86%)
copy archetypes/{jbehave-simple-archetype =>
jbehave-spring-archetype}/src/main/resources/archetype-resources/src/main/java/steps/MySteps.java
(100%)
copy
jbehave-spring/src/test/java/org/jbehave/core/steps/spring/steps-with-missing-dependency.xml
=>
archetypes/jbehave-spring-archetype/src/main/resources/archetype-resources/src/main/resources/my_steps.xml
(67%)
copy archetypes/{jbehave-simple-archetype =>
jbehave-spring-archetype}/src/main/resources/archetype-resources/src/main/resources/stories/my.story
(100%)
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-tutorial branch, master, updated. 38a8ecf7125d61525bc1cbdc5fb3c834f7076108
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-tutorial". The branch, master has been updated via 38a8ecf7125d61525bc1cbdc5fb3c834f7076108 (commit) from d1041d6d6e0722b02b10058ab9eacf71047e4e84 (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 38a8ecf7125d61525bc1cbdc5fb3c834f7076108 Author: Paul Hammant Date: Wed Apr 13 15:47:49 2011 -0500 upgrade groovy again (today's RC release) --- Summary of changes: pom.xml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- jbehave-tutorial To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-tutorial branch, master, updated. d1041d6d6e0722b02b10058ab9eacf71047e4e84
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-tutorial".
The branch, master has been updated
via d1041d6d6e0722b02b10058ab9eacf71047e4e84 (commit)
from 2e500b4747e24f7e127dc07111b9c92bb896e53e (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 d1041d6d6e0722b02b10058ab9eacf71047e4e84
Author: Paul Hammant
Date: Wed Apr 13 11:45:21 2011 -0500
undo of 'JBEHAVE-436: kludge for story location before this issue is fixed'
- 27f010e8d546f4764dfa2be5db0f45759fd2
---
Summary of changes:
etsy-stories/pom.xml | 36 +---
.../jbehave/tutorials/etsy/EtsyDotComStories.java |2 +-
.../{resources => }/stories/advanced_search.story |0
.../main/{resources => }/stories/etsy_browse.story |0
.../main/{resources => }/stories/etsy_cart.story |0
5 files changed, 2 insertions(+), 36 deletions(-)
rename etsy-stories/src/main/{resources => }/stories/advanced_search.story
(100%)
rename etsy-stories/src/main/{resources => }/stories/etsy_browse.story (100%)
rename etsy-stories/src/main/{resources => }/stories/etsy_cart.story (100%)
hooks/post-receive
--
jbehave-tutorial
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-tutorial branch, master, updated. 2e500b4747e24f7e127dc07111b9c92bb896e53e
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-tutorial". The branch, master has been updated via 2e500b4747e24f7e127dc07111b9c92bb896e53e (commit) from 5dd50be909f494920f224417a8167327e42430aa (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 2e500b4747e24f7e127dc07111b9c92bb896e53e Author: Paul Hammant Date: Wed Apr 13 10:15:53 2011 -0500 upgrade groovy --- Summary of changes: pom.xml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- jbehave-tutorial To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263458#action_263458 ] Jonathan Woods edited comment on JBEHAVE-424 at 4/13/11 9:34 AM: - This time, I've actually downloaded your sample (apologies for not trying the first time). At first glance, it looks as though it's because Eclipse unhelpfully merges compile and test scope, wrongly treating them the same; but Maven rightly doesn't. So your Spring config, which is test scope, simply isn't visible in the Maven runtime classpath. But I'll double-check and report back. was (Author: scintos): This time, I've actually downloaded your sample (apologies for not trying the first time). At first glance, it looks as though it's because Eclipse unhelpfully merges compile and test scope, but Maven doesn't. So your Spring config, which is test scope, simply isn't visible in the Maven runtime classpath. But I'll double-check and report back. > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263458#action_263458 ] Jonathan Woods commented on JBEHAVE-424: This time, I've actually downloaded your sample (apologies for not trying the first time). At first glance, it looks as though it's because Eclipse unhelpfully merges compile and test scope, but Maven doesn't. So your Spring config, which is test scope, simply isn't visible in the Maven runtime classpath. But I'll double-check and report back. > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263455#action_263455 ] Gardella Juan Pablo commented on JBEHAVE-424: - Hi Jon, Thanks for your time. Yes applicationContext.xml is in target\test-classes. You can download the sample and run mvn packate to reproduce the error. Juan > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263453#action_263453 ] Jonathan Woods commented on JBEHAVE-424: Juan - Have you really checked that applicationContext.xml is in target/test-classes? When this happens for me, it's because Eclipse/m2eclipse/Maven hasn't bothered to copy across the resource. Sometimes, modifying then saving it is enough to cause the copying to take place. Jon > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263451#action_263451 ] Gardella Juan Pablo commented on JBEHAVE-424: - Hi Mauro, First, thanks for your time. You can see the sample to reproduce the error. The file applicationContext.xml is in src/test/resources and is in classpath when maven run the tests. So your solution don't apply. Juan > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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-477) Upgrade Groovy dependency to 1.8-RC-3
Upgrade Groovy dependency to 1.8-RC-3 - Key: JBEHAVE-477 URL: http://jira.codehaus.org/browse/JBEHAVE-477 Project: JBehave Issue Type: Task Reporter: Paul Hammant Assignee: Paul Hammant Priority: Minor -- 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-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263447#action_263447 ] Mauro Talevi commented on JBEHAVE-424: -- The problem seems to suggest you're not adding the applicationContext.xml as a resource and therefore it never gets added to the classpath. To verify that this is the case simply look in target/classes after you've done a Maven build and see it the file is there. If not, configure your POM resources to add it. There are plenty of examples, e.g. a Spring security one, that may help you (http://jbehave.org/reference/stable/examples-philosophy.html). > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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-477) Upgrade Groovy dependency to 1.8-RC-3
[ http://jira.codehaus.org/browse/JBEHAVE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant resolved JBEHAVE-477. -- Resolution: Fixed > Upgrade Groovy dependency to 1.8-RC-3 > - > > Key: JBEHAVE-477 > URL: http://jira.codehaus.org/browse/JBEHAVE-477 > Project: JBehave > Issue Type: Task >Reporter: Paul Hammant >Assignee: Paul Hammant >Priority: Minor > -- 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-tutorial branch, master, updated. 5dd50be909f494920f224417a8167327e42430aa
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-tutorial". The branch, master has been updated via 5dd50be909f494920f224417a8167327e42430aa (commit) from 62e495409c3a12676134fb4dc59fba6fbb40b8e4 (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 5dd50be909f494920f224417a8167327e42430aa Author: Mauro Talevi Date: Wed Apr 13 13:20:46 2011 +0100 Archetypes move to jbehave-core from 3.4 --- Summary of changes: .../jbehave-junit-stories-archetype/pom.xml| 20 .../META-INF/maven/archetype-metadata.xml | 18 .../src/main/resources/archetype-resources/pom.xml | 101 .../src/main/java/MyStories.java | 82 .../src/main/java/steps/MySteps.java | 13 --- .../src/main/resources/stories/my.story| 10 -- .../resources/projects/basic/archetype.properties |4 - maven-archetypes/pom.xml | 37 --- 8 files changed, 0 insertions(+), 285 deletions(-) delete mode 100644 maven-archetypes/jbehave-junit-stories-archetype/pom.xml delete mode 100644 maven-archetypes/jbehave-junit-stories-archetype/src/main/resources/META-INF/maven/archetype-metadata.xml delete mode 100644 maven-archetypes/jbehave-junit-stories-archetype/src/main/resources/archetype-resources/pom.xml delete mode 100644 maven-archetypes/jbehave-junit-stories-archetype/src/main/resources/archetype-resources/src/main/java/MyStories.java delete mode 100644 maven-archetypes/jbehave-junit-stories-archetype/src/main/resources/archetype-resources/src/main/java/steps/MySteps.java delete mode 100644 maven-archetypes/jbehave-junit-stories-archetype/src/main/resources/archetype-resources/src/main/resources/stories/my.story delete mode 100644 maven-archetypes/jbehave-junit-stories-archetype/src/test/resources/projects/basic/archetype.properties delete mode 100644 maven-archetypes/jbehave-junit-stories-archetype/src/test/resources/projects/basic/goal.txt delete mode 100644 maven-archetypes/pom.xml hooks/post-receive -- jbehave-tutorial 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.3.2-3-g6da7c41
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 6da7c41cba4efd9f0139a815f60332857087bd0a (commit) from e5a8cdeba3dfe2148e6809c41ad026e57d73ab96 (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 6da7c41cba4efd9f0139a815f60332857087bd0a Author: Mauro Talevi Date: Wed Apr 13 13:14:57 2011 +0100 Updated release notes. --- Summary of changes: distribution/src/site/content/release-notes.html |6 -- 1 files changed, 4 insertions(+), 2 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-dev] [jira] Work started: (JBEHAVE-476) Archetypes to boostrap creation of projects
[ http://jira.codehaus.org/browse/JBEHAVE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-476 started by Mauro Talevi. > Archetypes to boostrap creation of projects > --- > > Key: JBEHAVE-476 > URL: http://jira.codehaus.org/browse/JBEHAVE-476 > Project: JBehave > Issue Type: New Feature >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-scm] jbehave-core branch, master, updated. jbehave-3.3.2-2-ge5a8cde
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 e5a8cdeba3dfe2148e6809c41ad026e57d73ab96 (commit) from c675f2200dfdacc8438376261be5ed20f517fc51 (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 e5a8cdeba3dfe2148e6809c41ad026e57d73ab96 Author: Mauro Talevi Date: Wed Apr 13 13:10:40 2011 +0100 JBEHAVE-476: Start of archetypes. Added simple archetype. --- Summary of changes: 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 | 45 +++--- .../src/main/java/steps/MySteps.java | 13 +++ .../src/main/resources/stories/my.story| 10 ++ archetypes/pom.xml | 47 + pom.xml|1 + 8 files changed, 222 insertions(+), 33 deletions(-) create mode 100644 archetypes/jbehave-simple-archetype/pom.xml create mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/META-INF/maven/archetype-metadata.xml create mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/archetype-resources/pom.xml copy examples/trader/src/main/java/org/jbehave/examples/trader/TraderStories.java => archetypes/jbehave-simple-archetype/src/main/resources/archetype-resources/src/main/java/MyStories.java (60%) create mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/archetype-resources/src/main/java/steps/MySteps.java create mode 100644 archetypes/jbehave-simple-archetype/src/main/resources/archetype-resources/src/main/resources/stories/my.story create mode 100644 archetypes/pom.xml 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] Created: (JBEHAVE-476) Archetypes to boostrap creation of projects
Archetypes to boostrap creation of projects --- Key: JBEHAVE-476 URL: http://jira.codehaus.org/browse/JBEHAVE-476 Project: JBehave Issue Type: New Feature 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] Created: (JBEHAVE-475) Groovy Stack traces not compressing for 1.8RC2.
Groovy Stack traces not compressing for 1.8RC2. --- Key: JBEHAVE-475 URL: http://jira.codehaus.org/browse/JBEHAVE-475 Project: JBehave Issue Type: Bug Components: Core Reporter: Paul Hammant Assignee: Paul Hammant Priority: Trivial Fix For: 3.3.2 -- 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-475) Groovy Stack traces not compressing for 1.8RC2.
[ http://jira.codehaus.org/browse/JBEHAVE-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant resolved JBEHAVE-475. -- Resolution: Fixed > Groovy Stack traces not compressing for 1.8RC2. > --- > > Key: JBEHAVE-475 > URL: http://jira.codehaus.org/browse/JBEHAVE-475 > Project: JBehave > Issue Type: Bug > Components: Core >Reporter: Paul Hammant >Assignee: Paul Hammant >Priority: Trivial > Fix For: 3.3.2 > > -- 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-355) Groovy bindings for steps
[ http://jira.codehaus.org/browse/JBEHAVE-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-355. -- Resolution: Duplicate Duplicate of JBEHAVE-365. > Groovy bindings for steps > - > > Key: JBEHAVE-355 > URL: http://jira.codehaus.org/browse/JBEHAVE-355 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Paul Hammant > > Adriano Bonat (ThoughtWorker) suggests that invoking step methods written in > Groovy would be cool. -- 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-1-gc675f22
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 c675f2200dfdacc8438376261be5ed20f517fc51 (commit) from a3f067700d47e0871a366a62c170539288582cf2 (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 c675f2200dfdacc8438376261be5ed20f517fc51 Author: Mauro Talevi Date: Wed Apr 13 10:00:12 2011 +0100 [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-groovy/pom.xml|2 +- jbehave-guice/pom.xml |2 +- jbehave-hudson-plugin/pom.xml |2 +- jbehave-maven-plugin/pom.xml |2 +- jbehave-pico/pom.xml |2 +- jbehave-spring/pom.xml|2 +- jbehave-weld/pom.xml |2 +- pom.xml |2 +- 11 files changed, 11 insertions(+), 11 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.3.2, created. jbehave-3.3.2
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.3.2 has been created at a7775a5548b1b238a84905377557ae04d6a7baac (tag) tagging a3f067700d47e0871a366a62c170539288582cf2 (commit) replaces jbehave-3.3.1 tagged by Mauro Talevi on Wed Apr 13 10:00:06 2011 +0100 - Log - [maven-release-plugin] copy for tag jbehave-3.3.2 Mauro Talevi (9): [maven-release-plugin] prepare for next development iteration Updated groovy example. Renamed groovy example. Updated groovy examples names to better reflect behaviour. Updated docs. JBEHAVE-474: Updated pending.story to verify that the problem cannot be reproduced. JBEHAVE-474: Refactored determination of previous non-And step. Step starting word functionality now provided by Keywords rather than CandidateStep, which may not be defined. JBEHAVE-474: Added a unit test to verify creation of pending steps when no candidate steps are found. Updated release notes. [maven-release-plugin] prepare release jbehave-3.3.2 --- 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.3.1-9-ga3f0677
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 a3f067700d47e0871a366a62c170539288582cf2 (commit) from 5f0150d2c828680c872d44f97107acb031a1e582 (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 a3f067700d47e0871a366a62c170539288582cf2 Author: Mauro Talevi Date: Wed Apr 13 09:59:31 2011 +0100 [maven-release-plugin] prepare release jbehave-3.3.2 --- Summary of changes: distribution/pom.xml |2 +- jbehave-ant/pom.xml |2 +- jbehave-core/pom.xml |2 +- jbehave-groovy/pom.xml|2 +- jbehave-guice/pom.xml |2 +- jbehave-hudson-plugin/pom.xml |2 +- jbehave-maven-plugin/pom.xml |2 +- jbehave-pico/pom.xml |2 +- jbehave-spring/pom.xml|2 +- jbehave-weld/pom.xml |2 +- pom.xml |2 +- 11 files changed, 11 insertions(+), 11 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
