Re: [jbehave-dev] A request to improve adoption

2011-05-13 Thread Mauro Talevi
Hi, the point of using Maven is that you don't need to build the jars, these are already available on Maven Central and will be automatically downloaded when you declare them in your pom.xml: http://repo2.maven.org/maven2/org/jbehave/jbehave-core/ If you don't use Maven, the binary distribution

[jbehave-dev] [jira] Updated: (JBEHAVE-489) AfterStories.xml and BeforeStories.xml being corrupt or zero length will break the Hudson plugin causing build failures after an otherwise successful JBehav

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-489: - Fix Version/s: 3.4 AfterStories.xml and BeforeStories.xml being corrupt or zero length will break

[jbehave-dev] [jira] Updated: (JBEHAVE-446) JBehave Reports import to Hudson xUnit Error: Conversion error Error to convert - A file not found

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-446: - Fix Version/s: 3.4 JBehave Reports import to Hudson xUnit Error: Conversion error Error to convert

[jbehave-dev] [jira] Updated: (JBEHAVE-498) withRelativeDirectory appears to be broken

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-498: - Affects Version/s: (was: web-3.3) Fix Version/s: 3.4 withRelativeDirectory appears to be

[jbehave-dev] [jira] Created: (JBEHAVE-512) GivenStories path list should be more tollerant with spaces

2011-05-13 Thread Mauro Talevi (JIRA)
GivenStories path list should be more tollerant with spaces --- Key: JBEHAVE-512 URL: http://jira.codehaus.org/browse/JBEHAVE-512 Project: JBehave Issue Type: Improvement

[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-4-5-gfbd2ce0

2011-05-13 Thread git version control
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 fbd2ce08b24fd8d397e0065d96cb8f281c13cea2 (commit) via

[jbehave-dev] [jira] Resolved: (JBEHAVE-512) GivenStories path list should be more tollerant with spaces

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-512. -- Resolution: Fixed GivenStories path list should be more tollerant with spaces

[jbehave-dev] [jira] Updated: (JBEHAVE-489) AfterStories.xml and BeforeStories.xml being corrupt or zero length will break the Hudson plugin

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-489: - Component/s: Core Description: AfterStories.xml can be zero bytes on occasion. BeforeStories.xml

[jbehave-dev] [jira] Commented: (JBEHAVE-425) Maven JBehave plugin goal jbehave:run-stories-as-embeddables doesn't found my JUnitStories test classes

2011-05-13 Thread Gavin Tranter (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=266613#action_266613 ] Gavin Tranter commented on JBEHAVE-425: --- I am also getting the same error message wit version

[jbehave-dev] [jira] Created: (JBEHAVE-513) @Before/AfterStories executions that have failed should be highlighted in red in the reports.hml entries

2011-05-13 Thread Mauro Talevi (JIRA)
@Before/AfterStories executions that have failed should be highlighted in red in the reports.hml entries Key: JBEHAVE-513 URL:

[jbehave-dev] [jira] Resolved: (JBEHAVE-492) CandidateSteps instances should be created by StoryRunner context allowing for multi-threaded stateful steps logic

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-492. -- Resolution: Fixed CandidateSteps instances should be created by StoryRunner context allowing for

[jbehave-dev] [jira] Resolved: (JBEHAVE-472) Improve state management of StoryRunner

2011-05-13 Thread Mauro Talevi (JIRA)
[ 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 ---

[jbehave-dev] [jira] Commented: (JBEHAVE-514) jbehave-maven-plugin ignoring execution

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=266635#action_266635 ] Mauro Talevi commented on JBEHAVE-514: -- Have you tried executing: {code} mvn clean install

[jbehave-dev] [jira] Commented: (JBEHAVE-514) jbehave-maven-plugin ignoring execution

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=266638#action_266638 ] Mauro Talevi commented on JBEHAVE-514: -- To run in Eclipse, install

[jbehave-dev] [jira] Commented: (JBEHAVE-514) jbehave-maven-plugin ignoring execution

2011-05-13 Thread Gavin Tranter (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=266643#action_266643 ] Gavin Tranter commented on JBEHAVE-514: --- Hi, Thank you for your prompt reply. I have both

[jbehave-dev] [jira] Commented: (JBEHAVE-514) jbehave-maven-plugin ignoring execution

2011-05-13 Thread Mauro Talevi (JIRA)
[ http://jira.codehaus.org/browse/JBEHAVE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=266655#action_266655 ] Mauro Talevi commented on JBEHAVE-514: -- Difficult to help you without seeing your full project.

RE: [jbehave-dev] A request to improve adoption

2011-05-13 Thread M CHILDS
I understand that maven collects dependencies and is useful. However, maven doesn't complete (I used mvn 2.2 this morning) with the provided pom.xml when I follow this process: 1. download stable core BIN distribution2. Unzip3. cd to lib folder4. mvn clean install If it worked, I would still

Re: [jbehave-dev] A request to improve adoption

2011-05-13 Thread Mauro Talevi
The process is: 1. download bin distribution 2. unzip 3. cd lib 4. ant copy-dependencies Then you have all your dependencies (direct and transitive) and can use them manually with Ant however you see fit. To be honest I don't see the big difference with what you're proposing. We won't package

RE: [jbehave-dev] A request to improve adoption

2011-05-13 Thread M CHILDS
When you see the bin distribution, it makes sense to you what is required to get started and get all needed jars. It seems easy and straightforward to you. To users new to jbehave and maven, who just want to go through an example or two on their machine to evaluate jbehave, it can take several

[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-4-8-g24c8d3e

2011-05-13 Thread git version control
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 24c8d3ec054c39154fa8f4caa8aef6343512c3d0 (commit) via

[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-4-10-g446cd08

2011-05-13 Thread git version control
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 446cd08ba887cf6f5b08a8eacc121240c96fcead (commit) via