[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
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Priority: Minor
 Fix For: 3.4


We should allow paths to be padded with spaces.

-- 
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.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  047a36305fb514db9c30d081255bf2d64ab29687 (commit)
   via  08398cd3c48ca0411fc9efafdd328024476f3398 (commit)
   via  221010cc61ce9d87171df01e05deaac5d0968019 (commit)
  from  7cf573656df9c215b4720263264c24e5415b97c3 (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 fbd2ce08b24fd8d397e0065d96cb8f281c13cea2
Author: Mauro Talevi 
Date:   Fri May 13 11:47:22 2011 +0100

JBEHAVE-512: GivenStories paths now trimmed.

commit 047a36305fb514db9c30d081255bf2d64ab29687
Author: Mauro Talevi 
Date:   Fri May 13 10:47:18 2011 +0100

JBEHAVE-489: AfterStories failures are now handled according to strategy 
and reportered to output.

commit 08398cd3c48ca0411fc9efafdd328024476f3398
Author: Mauro Talevi 
Date:   Fri May 13 10:59:03 2011 +0200

JBEHAVE-489: Ensured Before/AfterStories reports have complete XML.

commit 221010cc61ce9d87171df01e05deaac5d0968019
Author: Mauro Talevi 
Date:   Fri May 13 10:57:23 2011 +0200

JBEHAVE-492: Refactored trader embeddables to use the steps factory 
consistently.

---

Summary of changes:
 .../trader/FailingBeforeAfterTraderStories.java|   21 +++---
 .../trader/FailingBeforeAfterTraderStory.java  |   23 +++-
 .../org/jbehave/examples/trader/TraderStories.java |1 -
 .../org/jbehave/examples/trader/TraderStory.java   |7 -
 .../trader/stories/FailingAfterStories.java|   29 
 .../trader/stories/FailingBeforeStories.java   |   12 +++-
 ...e_stories.story => failing_after_stories.story} |2 +-
 .../org/jbehave/core/embedder/StoryRunner.java |   13 +
 .../java/org/jbehave/core/model/GivenStory.java|6 ++--
 .../jbehave/core/reporters/PrintStreamOutput.java  |2 +-
 .../core/parsers/RegexStoryParserBehaviour.java|4 +-
 11 files changed, 86 insertions(+), 34 deletions(-)
 create mode 100644 
examples/trader/src/main/java/org/jbehave/examples/trader/stories/FailingAfterStories.java
 copy 
examples/trader/src/main/java/org/jbehave/examples/trader/stories/{failing_before_stories.story
 => failing_after_stories.story} (55%)


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-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
> ---
>
> Key: JBEHAVE-512
> URL: http://jira.codehaus.org/browse/JBEHAVE-512
> Project: JBehave
>  Issue Type: Improvement
>Reporter: Mauro Talevi
>Assignee: Mauro Talevi
>Priority: Minor
> Fix For: 3.4
>
>
> We should allow paths to be padded with spaces.

-- 
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-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 can have invalid XML on occasion.



  was:
AfterStories.xml can be zero bytes on occasion.
BeforeStories.xml can have invalid XML on occasion.

I'll assume its zero length because there were no @AfterStories steps that were 
run for the job in question ( I guess there were @BeforeStories steps that were 
run)

Summary: AfterStories.xml and BeforeStories.xml being corrupt or zero 
length will break the Hudson plugin   (was: AfterStories.xml and 
BeforeStories.xml being corrupt or zero length will break the Hudson plugin 
causing build failures after an otherwise successful JBehave job)

> AfterStories.xml and BeforeStories.xml being corrupt or zero length will 
> break the Hudson plugin 
> -
>
> Key: JBEHAVE-489
> URL: http://jira.codehaus.org/browse/JBEHAVE-489
> Project: JBehave
>  Issue Type: Bug
>  Components: Core, Hudson Support
>Reporter: Paul Hammant
> Fix For: 3.4
>
>
> AfterStories.xml can be zero bytes on occasion.
> BeforeStories.xml can have invalid XML on occasion.

-- 
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-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 resolved JBEHAVE-489.
--

Resolution: Fixed

> AfterStories.xml and BeforeStories.xml being corrupt or zero length will 
> break the Hudson plugin 
> -
>
> Key: JBEHAVE-489
> URL: http://jira.codehaus.org/browse/JBEHAVE-489
> Project: JBehave
>  Issue Type: Bug
>  Components: Core, Hudson Support
>Reporter: Paul Hammant
> Fix For: 3.4
>
>
> AfterStories.xml can be zero bytes on occasion.
> BeforeStories.xml can have invalid XML on occasion.

-- 
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-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:comment-tabpanel&focusedCommentId=266605#action_266605
 ] 

Mauro Talevi commented on JBEHAVE-446:
--

Tested against 3.4-beta-4 and could not reproduce using the TraderJUnitRunner.  
The TraderEmbedderRunner looks a rather strange way to configure the stories 
and would not recommend it. 

Do note though that there is an issue with spaces in the given stories list, 
now fixed in JBEHAVE-512.   If you remove spaces, it will work.


> JBehave Reports import to Hudson xUnit Error: Conversion error Error to 
> convert - A file not found
> --
>
> Key: JBEHAVE-446
> URL: http://jira.codehaus.org/browse/JBEHAVE-446
> Project: JBehave
>  Issue Type: Bug
>  Components: Hudson Support
>Affects Versions: 3.2
>Reporter: Sven Schäfer
> Fix For: 3.4
>
> Attachments: jbehave-hudson-test-project.zip
>
>
> Hi,
> i know about some similar tasks JBEHAVE-394, but i think this does not 
> resolve my problem.
> In my test project(see Attachment) i added a 
> story(ist_produkt_in_bestand.story) with GivenStories. The report xml for 
> that story is currupted because two end-tags are missing. 
> That failure takes place with version 3.1.2, 3.2-beta 1..5, 3.2 and 
> 3.3-beta-1.
> I think it is realy possible that i doing something wrong with the 
> configuration "src/test/java...jbehave.config.TraderEmbedderRunner". If it 
> is, tell me pleace how i change it.
> My Hudson config:
> jbehave-hudson-plugin 3.2-beta-5
> xUnit 1.13
> Thanks for your help.
> Best regards
> Sven Schäfer

-- 
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. bb42bb146f15871f0277a82ac3f6fb2a4833cfde

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-tutorial".

The branch, master has been updated
   via  bb42bb146f15871f0277a82ac3f6fb2a4833cfde (commit)
  from  ea79c45e08bbc98b565e9adcbb0038422fcca581 (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 bb42bb146f15871f0277a82ac3f6fb2a4833cfde
Author: Paul Hammant 
Date:   Fri May 13 06:03:14 2011 -0500

Revert "illustrating issue with After/BeforeStories and story reporters"

This reverts commit ea79c45e08bbc98b565e9adcbb0038422fcca581.

---

Summary of changes:
 .../src/main/groovy/BeforeAfterSteps.groovy|   16 
 .../jbehave/tutorials/etsy/EtsyDotComStories.java  |4 +---
 2 files changed, 1 insertions(+), 19 deletions(-)
 delete mode 100644 etsy-stories/src/main/groovy/BeforeAfterSteps.groovy


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] Commented: (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:comment-tabpanel&focusedCommentId=266608#action_266608
 ] 

Mauro Talevi commented on JBEHAVE-498:
--

Derek, code location is not the same thing as report location.  The code 
location is used for other purposes and allows us to find the URL where the 
compiled code is.   The reports live in a relative directory of the code 
location. 

Could you see if you can reproduce your behaviour in a unit test? 



> withRelativeDirectory appears to be broken
> --
>
> Key: JBEHAVE-498
> URL: http://jira.codehaus.org/browse/JBEHAVE-498
> Project: JBehave
>  Issue Type: Bug
>  Components: Core
> Environment: Linux. Jdk6
>Reporter: Derek Clarkson
> Fix For: 3.4
>
>
> I'm working in a non maven environment. I attempted to set the output 
> directory for reports as follows
> public static class MyReportBuilder extends StoryReporterBuilder {
> public MyReportBuilder() {
> super();
> this.withRelativeDirectory("../build/publish/story-reports");
> this.withFormats(CONSOLE, HTML, XML);
> }
> }
> Upon running the JUnits I get the following:
> org.jbehave.core.reporters.FilePrintStreamFactory$PrintStreamCreationFailed: 
> Failed to create print stream for file 
> /home/derek/workspace/smsManagerGit/target/../build/publish/story-reports/BeforeStories.html
>   at 
> org.jbehave.core.reporters.FilePrintStreamFactory.createPrintStream(FilePrintStreamFactory.java:39)
>   at 
> org.jbehave.core.reporters.Format$4.createStoryReporter(Format.java:43)
>   at 
> org.jbehave.core.reporters.StoryReporterBuilder.reporterFor(StoryReporterBuilder.java:310)
>   at 
> org.jbehave.core.reporters.StoryReporterBuilder.build(StoryReporterBuilder.java:285)
>   at 
> org.jbehave.core.configuration.Configuration.storyReporter(Configuration.java:200)
>   at 
> org.jbehave.core.embedder.StoryRunner.runBeforeOrAfterStories(StoryRunner.java:58)
>   at 
> org.jbehave.core.embedder.Embedder.runStoriesAsPaths(Embedder.java:209)
>   at 
> au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder.run(AnnotatedStoryEmbedder.java:48)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>   at java.lang.reflect.Method.invoke(Method.java:597)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
>   at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
>   at 
> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49)
>   at 
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
>   at 
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: java.io.FileNotFoundException: 
> /home/derek/workspace/smsManagerGit/target/../build/publish/story-reports/BeforeStories.html
>  (No such file or directory)
>   at java.io.FileOutputStream.open(Native Method)
>   at java.io.FileOutputStream.(FileOutputStream.java:179)
>   at 
> org.jbehave.core.reporters.FilePrintStreamFactory$FilePrintStream.(FilePrintStreamFactory.java:137)
>   at 
> o

[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-4-6-gea23f5f

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  ea23f5fcf0d104675d09b186b2dd1e9744e97718 (commit)
  from  fbd2ce08b24fd8d397e0065d96cb8f281c13cea2 (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 ea23f5fcf0d104675d09b186b2dd1e9744e97718
Author: Mauro Talevi 
Date:   Fri May 13 12:41:20 2011 +0100

JBEHAVE-513: Failures in @Before/AfterStories now highlighted in red in the 
reports view.

---

Summary of changes:
 .../org/jbehave/ant/EmbedderTaskBehaviour.java |3 ++-
 .../core/reporters/FreemarkerViewGenerator.java|3 ++-
 .../org/jbehave/core/reporters/ReportsCount.java   |   10 --
 .../resources/ftl/jbehave-reports-with-totals.ftl  |5 +++--
 .../jbehave/core/embedder/EmbedderBehaviour.java   |   10 --
 .../core/embedder/EmbedderMonitorBehaviour.java|2 +-
 .../org/jbehave/mojo/EmbedderMojoBehaviour.java|3 ++-
 7 files changed, 22 insertions(+), 14 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] Resolved: (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) 

 [ 
http://jira.codehaus.org/browse/JBEHAVE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mauro Talevi resolved JBEHAVE-513.
--

Resolution: Fixed

> @Before/AfterStories executions that have failed should be highlighted in red 
> in the reports.hml entries
> 
>
> Key: JBEHAVE-513
> URL: http://jira.codehaus.org/browse/JBEHAVE-513
> Project: JBehave
>  Issue Type: Improvement
>  Components: Core
>Reporter: Mauro Talevi
>Assignee: Mauro Talevi
>Priority: Minor
> Fix For: 3.4
>
>
> These are executions that are not bound to scenarios.  The "failed" status in 
> the reports.html should be triggered by either failed scenarios or failed 
> 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] 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-tabpanel&focusedCommentId=266613#action_266613
 ] 

Gavin Tranter commented on JBEHAVE-425:
---

I am also getting the same error message wit version 3.3.2 of jbehave-core and 
jbehave-maven-plugin.

I get the error message:
org.jbehave.core.embedder.EmbedderClassLoader$InstantiationFailed: 
Instantiation failed for.svn/all-wcprops of type interface 
org.jbehave.core.Embeddable using class loader EmbedderClassLoader

I get this error when I run the goal jbehave:run-stories-as-embeddables


Could be my setup as I actual cant get the plugin to run the tests at all.

> Maven JBehave plugin goal jbehave:run-stories-as-embeddables doesn't found my 
> JUnitStories test classes
> ---
>
> Key: JBEHAVE-425
> URL: http://jira.codehaus.org/browse/JBEHAVE-425
> Project: JBehave
>  Issue Type: Bug
>  Components: Maven Plugin
>Affects Versions: web-3.2
> Environment: $ mvn --version
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_16
> Java home: C:\DEV\Java\jdk1.6.0_16\jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Marc Siramy
> Attachments: jBehavePluginConf.xml
>
>
> I'm testing a web site with Jbehave-web-selenium 3.2-beta-3 and I I'd rather 
> run my tests with jbehave-maven-plugin instead of running them with 
> maven-surefire-plugin, due to some issues of this last plugin with 
> jbehave-hudson-plugin (please see this issue for more information: 
> https://github.com/aparkinson/jbehave-hudson-plugin/issues#issue/1)
> But jbehave-maven-plugin doesn't recognize my JUnitStories test classes (that 
> seems to be always the case for plugin configurations given in JBEHAVE-207 
> issue (http://jira.codehaus.org/browse/JBEHAVE-207).
> Please the attached file for maven plugins configuration details.

-- 
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-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: http://jira.codehaus.org/browse/JBEHAVE-513
 Project: JBehave
  Issue Type: Improvement
  Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Priority: Minor
 Fix For: 3.4


These are executions that are not bound to scenarios.  The "failed" status in 
the reports.html should be triggered by either failed scenarios or failed 
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] 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 multi-threaded stateful steps logic
> --
>
> Key: JBEHAVE-492
> URL: http://jira.codehaus.org/browse/JBEHAVE-492
> Project: JBehave
>  Issue Type: New Feature
>  Components: Core
>Affects Versions: 3.x
>Reporter: Paul Hammant
>Assignee: Mauro Talevi
> Fix For: 3.4
>
>
> In multi-threaded mode, the steps instances need to be instantiated per 
> thread. 
> A way to do this is to pass the InjectableStepsFactory to the StoryRunner run 
> context and let the context instantiate the candidate steps per thread. 

-- 
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-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
> ---
>
> 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] Created: (JBEHAVE-514) jbehave-maven-plugin ignoring execution

2011-05-13 Thread Gavin Tranter (JIRA) 
jbehave-maven-plugin ignoring execution
---

 Key: JBEHAVE-514
 URL: http://jira.codehaus.org/browse/JBEHAVE-514
 Project: JBehave
  Issue Type: Bug
  Components: Maven Plugin
Affects Versions: web-3.3.2
 Environment: Ubuntu 10.4
Java 1.6
STS (Eclipse)
Maven 3.0-SNAPSHOT/0.10.0.201202009-0800)  (via STS) or
Apache Maven 2.2.1 (rdebian-1)
Java version: 1.6.0_22
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-31-generic" arch: "amd64" Family: "unix"

JBehave 3.3.2
jbehave-maven-plugin 3.3.2
Reporter: Gavin Tranter
Priority: Critical
 Fix For: 3.x


when trying to execute a package on a maven project with jbehave and 
jbehave-maven-plugin configured Maven fails to execute the jbehave goal.  This 
is regardless of weather I execute it with in Eclipse or on the commandline.

However if I issue the following command on the command line the 
jbehave-maven-plugin is executed and runs the acceptance tests:
mvn clean package 
org.jbehave:jbehave-maven-plugin:3.3.2:run-stories-as-embeddables

The command I use in Eclipse is:
jbehave:run-stories-as-embeddables

I have configured the jbehave plugin:

{noformat}


org.apache.maven.plugins
maven-compiler-plugin

1.6
1.6




org.jbehave
jbehave-maven-plugin
3.3.2


test

**/*.java



+author *
-skip



java.awt.headless
true



true
false




run-stories-as-embeddables
test


run-stories-as-embeddables






{noformat}

Thanks
Gavin


-- 
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-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-tabpanel&focusedCommentId=266635#action_266635
 ] 

Mauro Talevi commented on JBEHAVE-514:
--

Have you tried executing: 
{code}
mvn clean install
{code}
The Maven goal is bound by default to the integration-test phase, so you don't 
need to specify the goal.


> jbehave-maven-plugin ignoring execution
> ---
>
> Key: JBEHAVE-514
> URL: http://jira.codehaus.org/browse/JBEHAVE-514
> Project: JBehave
>  Issue Type: Bug
>  Components: Maven Plugin
>Affects Versions: web-3.3.2
> Environment: Ubuntu 10.4
> Java 1.6
> STS (Eclipse)
> Maven 3.0-SNAPSHOT/0.10.0.201202009-0800)  (via STS) or
> Apache Maven 2.2.1 (rdebian-1)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-31-generic" arch: "amd64" Family: "unix"
> JBehave 3.3.2
> jbehave-maven-plugin 3.3.2
>Reporter: Gavin Tranter
>Priority: Critical
> Fix For: 3.x
>
>
> when trying to execute a package on a maven project with jbehave and 
> jbehave-maven-plugin configured Maven fails to execute the jbehave goal.  
> This is regardless of weather I execute it with in Eclipse or on the 
> commandline.
> However if I issue the following command on the command line the 
> jbehave-maven-plugin is executed and runs the acceptance tests:
> mvn clean package 
> org.jbehave:jbehave-maven-plugin:3.3.2:run-stories-as-embeddables
> The command I use in Eclipse is:
> jbehave:run-stories-as-embeddables
> I have configured the jbehave plugin:
> {noformat}
>   
>   
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
>   1.6
>   1.6
>   
>   
>   
>   org.jbehave
>   jbehave-maven-plugin
>   3.3.2
>   
>   test
>   
>   **/*.java
>   
>   
>   +author *
>   -skip
>   
>   
>   
>   java.awt.headless
>   true
>   
>   
>   
> true
>   false
>   
>   
>   
>   run-stories-as-embeddables
>   test
>   
>   
> run-stories-as-embeddables
>   
>   
>   
>   
>   
> {noformat}
> Thanks
> Gavin

-- 
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-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-tabpanel&focusedCommentId=266638#action_266638
 ] 

Mauro Talevi commented on JBEHAVE-514:
--

To run in Eclipse, install http://m2eclipse.sonatype.org/ and execute 'Run As' 
... 'Maven install'

> jbehave-maven-plugin ignoring execution
> ---
>
> Key: JBEHAVE-514
> URL: http://jira.codehaus.org/browse/JBEHAVE-514
> Project: JBehave
>  Issue Type: Bug
>  Components: Maven Plugin
>Affects Versions: web-3.3.2
> Environment: Ubuntu 10.4
> Java 1.6
> STS (Eclipse)
> Maven 3.0-SNAPSHOT/0.10.0.201202009-0800)  (via STS) or
> Apache Maven 2.2.1 (rdebian-1)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-31-generic" arch: "amd64" Family: "unix"
> JBehave 3.3.2
> jbehave-maven-plugin 3.3.2
>Reporter: Gavin Tranter
>Priority: Critical
> Fix For: 3.x
>
>
> when trying to execute a package on a maven project with jbehave and 
> jbehave-maven-plugin configured Maven fails to execute the jbehave goal.  
> This is regardless of weather I execute it with in Eclipse or on the 
> commandline.
> However if I issue the following command on the command line the 
> jbehave-maven-plugin is executed and runs the acceptance tests:
> mvn clean package 
> org.jbehave:jbehave-maven-plugin:3.3.2:run-stories-as-embeddables
> The command I use in Eclipse is:
> jbehave:run-stories-as-embeddables
> I have configured the jbehave plugin:
> {noformat}
>   
>   
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
>   1.6
>   1.6
>   
>   
>   
>   org.jbehave
>   jbehave-maven-plugin
>   3.3.2
>   
>   test
>   
>   **/*.java
>   
>   
>   +author *
>   -skip
>   
>   
>   
>   java.awt.headless
>   true
>   
>   
>   
> true
>   false
>   
>   
>   
>   run-stories-as-embeddables
>   test
>   
>   
> run-stories-as-embeddables
>   
>   
>   
>   
>   
> {noformat}
> Thanks
> Gavin

-- 
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-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-tabpanel&focusedCommentId=266643#action_266643
 ] 

Gavin Tranter commented on JBEHAVE-514:
---

Hi,
Thank you for your prompt reply.
I have both tried mvn clean install and already have m2e installed.
I have included the out put from Run as ... Maven Install from eclipse:

[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building Portal Acceptance Tests 0.0.1-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.4.1:resources (default-resources) @ 
portal-acceptance ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ 
portal-acceptance ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.4.1:testResources (default-testResources) @ 
portal-acceptance ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] 
[INFO] --- maven-compiler-plugin:2.0.2:testCompile (default-testCompile) @ 
portal-acceptance ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.8.1:test (default-test) @ portal-acceptance 
---
[INFO] Surefire report directory: 
/home/gavintranter/Documents/blue/PortalAcceptance/target/surefire-reports
[INFO] 
[INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ portal-acceptance ---
[INFO] 
[INFO] --- maven-install-plugin:2.3:install (default-install) @ 
portal-acceptance ---
[INFO] Skipped re-installing 
/home/gavintranter/Documents/blue/PortalAcceptance/target/portal-acceptance-0.0.1-SNAPSHOT.jar
 to 
/home/gavintranter/.m2/repository/xxx//portal-acceptance/0.0.1-SNAPSHOT/portal-acceptance-0.0.1-SNAPSHOT.jar,
 seems unchanged
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 1.951s
[INFO] Finished at: Fri May 13 15:43:49 BST 2011
[INFO] Final Memory: 7M/164M
[INFO] 




> jbehave-maven-plugin ignoring execution
> ---
>
> Key: JBEHAVE-514
> URL: http://jira.codehaus.org/browse/JBEHAVE-514
> Project: JBehave
>  Issue Type: Bug
>  Components: Maven Plugin
>Affects Versions: web-3.3.2
> Environment: Ubuntu 10.4
> Java 1.6
> STS (Eclipse)
> Maven 3.0-SNAPSHOT/0.10.0.201202009-0800)  (via STS) or
> Apache Maven 2.2.1 (rdebian-1)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-31-generic" arch: "amd64" Family: "unix"
> JBehave 3.3.2
> jbehave-maven-plugin 3.3.2
>Reporter: Gavin Tranter
>Priority: Critical
> Fix For: 3.x
>
>
> when trying to execute a package on a maven project with jbehave and 
> jbehave-maven-plugin configured Maven fails to execute the jbehave goal.  
> This is regardless of weather I execute it with in Eclipse or on the 
> commandline.
> However if I issue the following command on the command line the 
> jbehave-maven-plugin is executed and runs the acceptance tests:
> mvn clean package 
> org.jbehave:jbehave-maven-plugin:3.3.2:run-stories-as-embeddables
> The command I use in Eclipse is:
> jbehave:run-stories-as-embeddables
> I have configured the jbehave plugin:
> {noformat}
>   
>   
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
>   1.6
>   1.6
>   
>   
>   
>   org.jbehave
>   jbehave-maven-plugin
>   3.3.2
>   
>   test
>   
>   **/*.java
>   
>   
>   +author *
>   -skip
>   
>   
>   
>   java.awt.headless
>   true
>   
>   
>   
> true
>   false
>   
>   
>

[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-tabpanel&focusedCommentId=266655#action_266655
 ] 

Mauro Talevi commented on JBEHAVE-514:
--

Difficult to help you without seeing your full project.  You could either 
upload the simplified project (simplest possible the reproduces the problem) or 
you could generate a working project using an archetype - a new feature of 3.4 
(see http://jbehave.org/reference/preview/archetypes.html).

> jbehave-maven-plugin ignoring execution
> ---
>
> Key: JBEHAVE-514
> URL: http://jira.codehaus.org/browse/JBEHAVE-514
> Project: JBehave
>  Issue Type: Bug
>  Components: Maven Plugin
>Affects Versions: web-3.3.2
> Environment: Ubuntu 10.4
> Java 1.6
> STS (Eclipse)
> Maven 3.0-SNAPSHOT/0.10.0.201202009-0800)  (via STS) or
> Apache Maven 2.2.1 (rdebian-1)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-31-generic" arch: "amd64" Family: "unix"
> JBehave 3.3.2
> jbehave-maven-plugin 3.3.2
>Reporter: Gavin Tranter
>Priority: Critical
> Fix For: 3.x
>
>
> when trying to execute a package on a maven project with jbehave and 
> jbehave-maven-plugin configured Maven fails to execute the jbehave goal.  
> This is regardless of weather I execute it with in Eclipse or on the 
> commandline.
> However if I issue the following command on the command line the 
> jbehave-maven-plugin is executed and runs the acceptance tests:
> mvn clean package 
> org.jbehave:jbehave-maven-plugin:3.3.2:run-stories-as-embeddables
> The command I use in Eclipse is:
> jbehave:run-stories-as-embeddables
> I have configured the jbehave plugin:
> {noformat}
>   
>   
>   org.apache.maven.plugins
>   maven-compiler-plugin
>   
>   1.6
>   1.6
>   
>   
>   
>   org.jbehave
>   jbehave-maven-plugin
>   3.3.2
>   
>   test
>   
>   **/*.java
>   
>   
>   +author *
>   -skip
>   
>   
>   
>   java.awt.headless
>   true
>   
>   
>   
> true
>   false
>   
>   
>   
>   run-stories-as-embeddables
>   test
>   
>   
> run-stories-as-embeddables
>   
>   
>   
>   
>   
> {noformat}
> Thanks
> Gavin

-- 
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

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 think the download page could use a 'here are the 4 
steps you take to get the final jar(s), after you install maven'.
Further, as valuable as maven is and ant + manual dependencies is, it sure 
would be nice to download 'jbehave-core.jar' and 'jbehave-dependencies.jar' in 
a single zip file and just drop those two jars into my classpath.
This would benefit you. If people give up building because they can't get 
things working, then you're losing potential adopters.


Date: Fri, 13 May 2011 08:22:41 +0200
From: mauro.tal...@aquilonia.org
To: dev@jbehave.codehaus.org
Subject: Re: [jbehave-dev] A request to improve adoption



  



  
  
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 includes an Ant
build.xml to allow you to copy all dependencies locally:



http://jbehave.org/reference/preview/dependencies.html



$cd lib

$ant copy-dependencies



If you are trying to build from source then you can find the build
instructions: 



http://jbehave.org/reference/preview/building-source.html



Also, current build requires Maven 2.2.x and the site part has not
been fully migrated to 3.0.x (which is the major non-compat of Maven
2->3). 



Cheers



On 13/05/2011 05:32, M CHILDS wrote:

  
  Could the binary release (I'm using 3.3.2) include a
fully built jar file? I think this will improve the chances of
people checking out and adopting jbehave.
  
  
  I request this because I've spent several hours and
haven't gotten the binary release to build into something I can
drop into my project. Each issue requires me to learn something
brand new, so it is very frustrating, because all I want to do
is start using jbehave.
  

  
  The remaining information is for troubleshooting. I'm not
sure this is the correct list for troubleshooting, but I've
included it in case it is.
  

  
  I am brand new to maven and jbehave. I ran this command
under release/lib:
  

  
  mvn clean install
  
  
  The first issue is the weld-se 1.1.0Final jar not being
available in the repositories by default (so I added the repo).
Known issue.
  The second is unsolved, and is this:
  

  
  
[ERROR]
  Failed to execute goal
  org.codehaus.xsite:xsite-maven-plugin:1.2:run (default) on
  project jbehave-distribution: Failed to run xsite:
  NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException:
  Failed to execute goal
  org.codehaus.xsite:xsite-maven-plugin:1.2:run (default) on
  project jbehave-distribution: Failed to run xsite
 
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
 
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
 
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
 
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
 
at
  org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
 
at
  org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
 
at
  org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
 
at
  org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
 
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
  Method)
 
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces

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 all the dependencies in a single jar - it's plainly a
bad practice for a number of reasons.   But you are free to do so if you
so wish once you have executed step 4 above.

Cheers

On 13/05/2011 16:28, M CHILDS wrote:
> 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 distribution
> 2. Unzip
> 3. cd to lib folder
> 4. mvn clean install
>
> If it worked, I would still think the download page could use a 'here
> are the 4 steps you take to get the final jar(s), after you install
> maven'.
>
> Further, as valuable as maven is and ant + manual dependencies is, it
> sure would be nice to download 'jbehave-core.jar' and
> 'jbehave-dependencies.jar' in a single zip file and just drop those
> two jars into my classpath.
>
> This would benefit you. If people give up building because they can't
> get things working, then you're losing potential adopters.
>
>
>
> 
> Date: Fri, 13 May 2011 08:22:41 +0200
> From: mauro.tal...@aquilonia.org
> To: dev@jbehave.codehaus.org
> Subject: Re: [jbehave-dev] A request to improve adoption
>
> 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 includes an Ant
> build.xml to allow you to copy all dependencies locally:
>
> http://jbehave.org/reference/preview/dependencies.html
>
> $cd lib
> $ant copy-dependencies
>
> If you are trying to build from source then you can find the build
> instructions:
>
> http://jbehave.org/reference/preview/building-source.html
>
> Also, current build requires Maven 2.2.x and the site part has not
> been fully migrated to 3.0.x (which is the major non-compat of Maven
> 2->3).
>
> Cheers
>
> On 13/05/2011 05:32, M CHILDS wrote:
>
> Could the binary release (I'm using 3.3.2) include a fully built
> jar file? I think this will improve the chances of people checking
> out and adopting jbehave.
>
> I request this because I've spent several hours and haven't gotten
> the binary release to build into something I can drop into my
> project. Each issue requires me to learn something brand new, so
> it is very frustrating, because all I want to do is start using
> jbehave.
>
> The remaining information is for troubleshooting. I'm not sure
> this is the correct list for troubleshooting, but I've included it
> in case it is.
>
> I am brand new to maven and jbehave. I ran this command under
> release/lib:
>
> mvn clean install
>
> The first issue is the weld-se 1.1.0Final jar not being available
> in the repositories by default (so I added the repo). Known issue.
> The second is unsolved, and is this:
>
> [ERROR] Failed to execute goal
> org.codehaus.xsite:xsite-maven-plugin:1.2:run (default) on project
> jbehave-distribution: Failed to run xsite: NullPointerException ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.codehaus.xsite:xsite-maven-plugin:1.2:run
> (default) on project jbehave-distribution: Failed to run xsite
> at
> 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at
> 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeM

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 hours just to get 
it working.
On the other hand, users were able to download a zip of all the jars, it 
becomes a very straightforward matter for them and takes no time.
In this way, users are more likely to evaluate jbehave and have a feeling of 
success and ease with it.

Date: Fri, 13 May 2011 16:34:41 +0100
From: mauro.tal...@aquilonia.org
To: dev@jbehave.codehaus.org
Subject: Re: [jbehave-dev] A request to improve adoption



  



  
  
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 all the dependencies in a single jar - it's plainly
a bad practice for a number of reasons.   But you are free to do so
if you so wish once you have executed step 4 above. 



Cheers



On 13/05/2011 16:28, M CHILDS wrote:

  
  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 distribution
  2. Unzip
  3. cd to lib folder
  4. mvn clean install
  



If it worked, I would still think the download page could
  use a 'here are the 4 steps you take to get the final jar(s),
  after you install maven'.



Further, as valuable as maven is and ant + manual
  dependencies is, it sure would be nice to download
  'jbehave-core.jar' and 'jbehave-dependencies.jar' in a single
  zip file and just drop those two jars into my classpath.

  

  
  This would benefit you. If people give up building
because they can't get things working, then you're losing
potential adopters.
  

  
  



Date: Fri, 13 May 2011 08:22:41 +0200

From: mauro.tal...@aquilonia.org

To: dev@jbehave.codehaus.org

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





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 includes an
Ant build.xml to allow you to copy all dependencies locally:



http://jbehave.org/reference/preview/dependencies.html



$cd lib

$ant copy-dependencies



If you are trying to build from source then you can find the
build instructions: 



http://jbehave.org/reference/preview/building-source.html



Also, current build requires Maven 2.2.x and the site part
has not been fully migrated to 3.0.x (which is the major
non-compat of Maven 2->3). 



Cheers



On 13/05/2011 05:32, M CHILDS wrote:

  
  Could the binary release (I'm using
3.3.2) include a fully built jar file? I think this will
improve the chances of people checking out and adopting
jbehave.
  
  
  I request this because I've spent
several hours and haven't gotten the binary release to
build into something I can drop into my project. Each
issue requires me to learn something brand new, so it is
very frustrating, because all I want to do is start
using jbehave.
  

  
  The remaining information is for
troubleshooting. I'm not sure this is the correct list
for troubleshooting, but I've included it in case it is.
  

  
  I am brand new to maven and
jbehave. I ran this command under release/lib:
  

  
  mvn clean install
  
  
  The first issue is the weld-se
1.1.0Final j

[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  415b212ae747c7530d757cff64ee754562633091 (commit)
  from  ea23f5fcf0d104675d09b186b2dd1e9744e97718 (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 24c8d3ec054c39154fa8f4caa8aef6343512c3d0
Author: Mauro Talevi 
Date:   Fri May 13 18:06:21 2011 +0100

JBEHAVE-476: Renamed archetype test project.

commit 415b212ae747c7530d757cff64ee754562633091
Author: Mauro Talevi 
Date:   Fri May 13 18:02:05 2011 +0100

JBEHAVE-476: Added archetype integration-test resources.

---

Summary of changes:
 archetypes/pom.xml |6 ++
 .../resources/projects/sample/archetype.properties |5 +
 .../src/test/resources/projects/sample/goal.txt|0
 3 files changed, 11 insertions(+), 0 deletions(-)
 create mode 100644 
archetypes/src/test/resources/projects/sample/archetype.properties
 copy jbehave-ant/src/test/java/org/jbehave/ant/stories/first.story => 
archetypes/src/test/resources/projects/sample/goal.txt (100%)
 mode change 100755 => 100644


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.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  9a6593f082c29b62be474fc74a557ef88eb2cb69 (commit)
  from  24c8d3ec054c39154fa8f4caa8aef6343512c3d0 (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 446cd08ba887cf6f5b08a8eacc121240c96fcead
Merge: 9a6593f082c29b62be474fc74a557ef88eb2cb69 
24c8d3ec054c39154fa8f4caa8aef6343512c3d0
Author: Paul Hammant 
Date:   Fri May 13 12:53:56 2011 -0500

Merge branch 'master' of ssh://git.codehaus.org/jbehave-core

commit 9a6593f082c29b62be474fc74a557ef88eb2cb69
Author: Paul Hammant 
Date:   Fri May 13 12:20:29 2011 -0500

eliminate Before and After Stories from xref

---

Summary of changes:
 .../org/jbehave/core/reporters/CrossReference.java |   14 +-
 1 files changed, 9 insertions(+), 5 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

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

2011-05-13 Thread Cristiano Gavião 

Hi,

I think the problem stated here it's just a matter of *reading the 
docs*... and of course, learn to build the code using ant or maven (this 
is nothing to do with jbehave humm)... 
http://jbehave.org/reference/stable/building-source.html


I think If you don't know how to use some of supported building tools, 
probably you won't be able to use jbehave at all..


If your desire is to run some example, just download the source and run 
this (using maven): mvn install -s settings.xml


Running that, you will see that ALL unit test created for jbehave will 
be running, showing that almost all of jbehave features is tested and is 
ok...


This won't take you more than a feel minutes...

Then go to examples directory and study the trader samples...

again, the docs is there to help you:  
http://jbehave.org/reference/stable/running-examples.html


regards

Cristiano


On 13/05/11 13:13, M CHILDS wrote:
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 hours just to get it working.


On the other hand, users were able to download a zip of all the jars, 
it becomes a very straightforward matter for them and takes no time.


In this way, users are more likely to evaluate jbehave and have a 
feeling of success and ease with it.



Date: Fri, 13 May 2011 16:34:41 +0100
From: mauro.tal...@aquilonia.org
To: dev@jbehave.codehaus.org
Subject: Re: [jbehave-dev] A request to improve adoption

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 all the dependencies in a single jar - it's plainly a 
bad practice for a number of reasons.   But you are free to do so if 
you so wish once you have executed step 4 above.


Cheers

On 13/05/2011 16:28, M CHILDS wrote:

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 distribution
2. Unzip
3. cd to lib folder
4. mvn clean install

If it worked, I would still think the download page could use a
'here are the 4 steps you take to get the final jar(s), after you
install maven'.

Further, as valuable as maven is and ant + manual dependencies is,
it sure would be nice to download 'jbehave-core.jar' and
'jbehave-dependencies.jar' in a single zip file and just drop
those two jars into my classpath.

This would benefit you. If people give up building because they
can't get things working, then you're losing potential adopters.




Date: Fri, 13 May 2011 08:22:41 +0200
From: mauro.tal...@aquilonia.org 
To: dev@jbehave.codehaus.org 
Subject: Re: [jbehave-dev] A request to improve adoption

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 includes an Ant
build.xml to allow you to copy all dependencies locally:

http://jbehave.org/reference/preview/dependencies.html

$cd lib
$ant copy-dependencies

If you are trying to build from source then you can find the build
instructions:

http://jbehave.org/reference/preview/building-source.html

Also, current build requires Maven 2.2.x and the site part has not
been fully migrated to 3.0.x (which is the major non-compat of
Maven 2->3).

Cheers

On 13/05/2011 05:32, M CHILDS wrote:

Could the binary release (I'm using 3.3.2) include a fully
built jar file? I think this will improve the chances of
people checking out and adopting jbehave.

I request this because I've spent several hours and haven't
gotten the binary release to build into something I can drop
into my project. Each issue requires me to learn something
brand new, so it is very frustrating, because all I want to do
is start using jbehave.

The remaining information is for troubleshooting. I'm not sure
this is the correct list for troubleshooting, but I've
included it in case it is.

I am brand new to maven and jbehave. I ran this command unde

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

2011-05-13 Thread m_chi...@msn.com 
It isn't. Ok, nevermind

Cristiano Gavião  wrote:

>Hi,
>
>I think the problem stated here it's just a matter of *reading the 
>docs*... and of course, learn to build the code using ant or maven (this 
>is nothing to do with jbehave humm)... 
>http://jbehave.org/reference/stable/building-source.html
>
>I think If you don't know how to use some of supported building tools, 
>probably you won't be able to use jbehave at all..
>
>If your desire is to run some example, just download the source and run 
>this (using maven): mvn install -s settings.xml
>
>Running that, you will see that ALL unit test created for jbehave will 
>be running, showing that almost all of jbehave features is tested and is 
>ok...
>
>This won't take you more than a feel minutes...
>
>Then go to examples directory and study the trader samples...
>
>again, the docs is there to help you:  
>http://jbehave.org/reference/stable/running-examples.html
>
>regards
>
>Cristiano
>
>
>On 13/05/11 13:13, M CHILDS wrote:
>> 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 hours just to get it working.
>>
>> On the other hand, users were able to download a zip of all the jars, 
>> it becomes a very straightforward matter for them and takes no time.
>>
>> In this way, users are more likely to evaluate jbehave and have a 
>> feeling of success and ease with it.
>>
>> 
>> Date: Fri, 13 May 2011 16:34:41 +0100
>> From: mauro.tal...@aquilonia.org
>> To: dev@jbehave.codehaus.org
>> Subject: Re: [jbehave-dev] A request to improve adoption
>>
>> 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 all the dependencies in a single jar - it's plainly a 
>> bad practice for a number of reasons.   But you are free to do so if 
>> you so wish once you have executed step 4 above.
>>
>> Cheers
>>
>> On 13/05/2011 16:28, M CHILDS wrote:
>>
>> 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 distribution
>> 2. Unzip
>> 3. cd to lib folder
>> 4. mvn clean install
>>
>> If it worked, I would still think the download page could use a
>> 'here are the 4 steps you take to get the final jar(s), after you
>> install maven'.
>>
>> Further, as valuable as maven is and ant + manual dependencies is,
>> it sure would be nice to download 'jbehave-core.jar' and
>> 'jbehave-dependencies.jar' in a single zip file and just drop
>> those two jars into my classpath.
>>
>> This would benefit you. If people give up building because they
>> can't get things working, then you're losing potential adopters.
>>
>>
>>
>> 
>> Date: Fri, 13 May 2011 08:22:41 +0200
>> From: mauro.tal...@aquilonia.org 
>> To: dev@jbehave.codehaus.org 
>> Subject: Re: [jbehave-dev] A request to improve adoption
>>
>> 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 includes an Ant
>> build.xml to allow you to copy all dependencies locally:
>>
>> http://jbehave.org/reference/preview/dependencies.html
>>
>> $cd lib
>> $ant copy-dependencies
>>
>> If you are trying to build from source then you can find the build
>> instructions:
>>
>> http://jbehave.org/reference/preview/building-source.html
>>
>> Also, current build requires Maven 2.2.x and the site part has not
>> been fully migrated to 3.0.x (which is the major non-compat of
>> Maven 2->3).
>>
>> Cheers
>>
>> On 13/05/2011 05:32, M CHILDS wrote:
>>
>> Could the binary release (I'm using 3.3.2) include a fully
>> built jar file? I think this will improve the chances of
>> people checking out and adopting jbehave.
>>
>> I request this because I've spent several hours and haven't
>> gotten the binary release to build into something I can drop
>> into my project. Each issue requires me to learn