[jbehave-dev] [jira] Created: (JBEHAVE-505) Ant tasks running with incorrect classpath
Ant tasks running with incorrect classpath -- Key: JBEHAVE-505 URL: http://jira.codehaus.org/browse/JBEHAVE-505 Project: JBehave Issue Type: Bug Components: Ant Tasks Affects Versions: web-3.2 Reporter: Derek Clarkson I've been trying to make this work for hours now. It appears that the Ant tasks run the Embedders with the classpath used to run Ant and that there is no way to override this. This means I cannot run JBehave against the classpaths used to build and test the application. How do we specify a classpath for JBEhave's Ant tasks -- 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-502) Add installation instructions to website documentation
[ http://jira.codehaus.org/browse/JBEHAVE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265548#action_265548 ] Mauro Talevi commented on JBEHAVE-502: -- Derek, in the lib directory binary distribution there is an Ant script with a target to copy all the dependencies using the latest up-to-date POM (c.f. the docs/dependencies.html). The Maven POM provides the meta-info about the dependencies, which can then be interpreted by the tool used for dependency management, Ivy or Maven Ant Tasks. > Add installation instructions to website documentation > -- > > Key: JBEHAVE-502 > URL: http://jira.codehaus.org/browse/JBEHAVE-502 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Derek Clarkson > > I've been scouring the site for a couple of days trying to figure out what I > needed to install and where. I'm not using maven. The website doesn't give > any idea of how to setup JBehave when not in a maven environment. So I'm > having to do it by reverse engineering the maven pom. > The first problem was to trying and figure out what to download. The linked > download file is only of use in a maven world. So I had to start downloaded > by surfing the online repos. So I'd suggest that the raw jars and zips should > also be linked for download from the main site. > The second issue was what to unzip, etc and suggested directories. Again the > documentation takes a "it will just work" approach, which it doesn't. So > instructions are needed here to. -- 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-501) Report stying not being generated
[
http://jira.codehaus.org/browse/JBEHAVE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265549#action_265549
]
Mauro Talevi commented on JBEHAVE-501:
--
The trader example has an Ant build script that you can use as a template to
get you started. It downloads the reports resources using the Maven Ant Tasks
but you can also do it manually.
The latest version of the site resources is indeed 3.1.1 - the version is not
linked to the version of core or web.
> Report stying not being generated
> -
>
> Key: JBEHAVE-501
> URL: http://jira.codehaus.org/browse/JBEHAVE-501
> Project: JBehave
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.3.2
> Environment: Ant, Eclipse, JDK6
>Reporter: Derek Clarkson
>
> I am using this report builder definition in a annotation setup as per the
> JBehave website documentation:
> public static class MyReportBuilder extends StoryReporterBuilder {
> public MyReportBuilder() {
> super();
>
> this.withCodeLocation(CodeLocations.codeLocationFromPath("build/publish/x"));
> this.withRelativeDirectory("story-reports");
> this.withDefaultFormats();
> this.withFormats(CONSOLE, HTML);
> }
> }
> The reports are being generated in the view directory, however there are no
> images, css or javascript being generated even though the html refers to
> them. I've scoured the web site documentation which suggests that they should
> be and tells you how to turn them off, but not what to do if they are not
> there.
--
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-2-29-g0cb27ba
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 0cb27bac426dbd56288bd51ac648a41010c97d89 (commit) from 557b4a9b317add9165f25950ec66ed757bf902b2 (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 0cb27bac426dbd56288bd51ac648a41010c97d89 Author: Mauro Talevi Date: Tue May 3 09:40:14 2011 +0200 JBEHAVE-501: Updated trader Ant script to show reports styling being generated. --- Summary of changes: examples/trader/build.xml |6 ++ 1 files changed, 2 insertions(+), 4 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] Created: (JBEHAVE-506) Allow system properties to be specified for AnnotatedEmbedderRunner
Allow system properties to be specified for AnnotatedEmbedderRunner --- Key: JBEHAVE-506 URL: http://jira.codehaus.org/browse/JBEHAVE-506 Project: JBehave Issue Type: Improvement Components: Core Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For: 3.4 The AnnotatedEmbedderRunner is missing the specification of system properties via the @UsingEmbedder. -- 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-2-30-g9e558c0
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 9e558c053a740b74dde3bd00b6aab572417abd1c (commit)
from 0cb27bac426dbd56288bd51ac648a41010c97d89 (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 9e558c053a740b74dde3bd00b6aab572417abd1c
Author: Mauro Talevi
Date: Tue May 3 10:43:16 2011 +0200
JBEHAVE-506: Added specification of system properties to @UsingEmbedder
for use by AnnotatedEmbedderRunners.
---
Summary of changes:
examples/{trader => trader-annotations}/build.xml | 18 --
examples/trader-annotations/pom.xml|2 +-
.../annotations/TraderAnnotatedEmbedder.java |2 +-
.../annotations/TraderAnnotatedPathRunner.java |2 +-
examples/trader/build.xml |3 ++-
.../jbehave/core/annotations/UsingEmbedder.java|1 +
.../core/configuration/AnnotationBuilder.java | 15 +++
.../configuration/AnnotationBuilderBehaviour.java |4 +++-
8 files changed, 28 insertions(+), 19 deletions(-)
copy examples/{trader => trader-annotations}/build.xml (60%)
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] Updated: (JBEHAVE-504) Ant task RunStoriesWithAnnotatedEmbedderRunner not passing system properties to embedder
[
http://jira.codehaus.org/browse/JBEHAVE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-504:
-
Description:
I'm trying to run JBehave from Ant using the following ant code:
{code:xml}
{code}
At the momment I'm getting a class not found which the story embedder I've
written starts up (doesn't happen from a junit run inside eclipse!).
I think that it's running from the default directory because it appears that
the systemProperties are not making it through to the embedder. Here's the log
showing the startup:
{code}
run-bdd-tests:
[runStoriesWithAnnotatedEmbedderRunner] Running stories with annotated embedder
org.jbehave.core.junit.AnnotatedEmbedderRunner
[runStoriesWithAnnotatedEmbedderRunner] Found class names :
[au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder]
[runStoriesWithAnnotatedEmbedderRunner] 2011-05-03 16:12:21,042 DEBUG
[runStoriesWithAnnotatedEmbedderRunner] Processing system properties {}
{code}
As you can see it's reporting no properties passed. Digging into the Ant task
code supports that the properties are not getting through, but from what I can
see in the source there is no obvious reason. Possibly the code that loads the
properties has a bug and is throwing an exception because it's try-catch
silently swallows any errors.
was:
I'm trying to run JBehave from Ant using the following ant code:
{code:ant}
{code}
At the momment I'm getting a class not found which the story embedder I've
written starts up (doesn't happen from a junit run inside eclipse!).
I think that it's running from the default directory because it appears that
the systemProperties are not making it through to the embedder. Here's the log
showing the startup:
{code}
run-bdd-tests:
[runStoriesWithAnnotatedEmbedderRunner] Running stories with annotated embedder
org.jbehave.core.junit.AnnotatedEmbedderRunner
[runStoriesWithAnnotatedEmbedderRunner] Found class names :
[au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder]
[runStoriesWithAnnotatedEmbedderRunner] 2011-05-03 16:12:21,042 DEBUG
[runStoriesWithAnnotatedEmbedderRunner] Processing system properties {}
{code}
As you can see it's reporting no properties passed. Digging into the Ant task
code supports that the properties are not getting through, but from what I can
see in the source there is no obvious reason. Possibly the code that loads the
properties has a bug and is throwing an exception because it's try-catch
silently swallows any errors.
Affects Version/s: (was: web-3.2)
3.3.2
> Ant task RunStoriesWithAnnotatedEmbedderRunner not passing system properties
> to embedder
>
>
> Key: JBEHAVE-504
> URL: http://jira.codehaus.org/browse/JBEHAVE-504
> Project: JBehave
> Issue Type: Bug
> Components: Ant Tasks
>Affects Versions: 3.3.2
> Environment: Ant
>Reporter: Derek Clarkson
>
> I'm trying to run JBehave from Ant using the following ant code:
> {code:xml}
> classname="org.jbehave.ant.RunStoriesWithAnnotatedEmbedderRunner"
> classpathref="integration.tests.classpath" />
> sourceDirectory="src/integration"
>
> systemProperties="java.awt.headless=true,web.project.dir=${build.integration.web.dir}"
>
> ignoreFailureInStories="true"
> ignoreFailureInView="false"
> generateViewAfterStories="true" />
> {code}
> At the momment I'm getting a class not found which the story embedder I've
> written starts up (doesn't happen from a junit run inside eclipse!).
> I think that it's running from the default directory because it appears that
> the systemProperties are not making it through to the embedder. Here's the
> log showing the startup:
> {code}
> run-bdd-tests:
> [runStoriesWithAnnotatedEmbedderRunner] Running stories with annotated
> embedder org.jbehave.core.junit.AnnotatedEmbedderRunner
> [runStoriesWithAnnotatedEmbedderRunner] Found class names :
> [au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder]
> [runStoriesWithAnnotatedEmbedderRunner] 2011-05-03 16:12:21,042 DEBUG
> [runStoriesWithAnnotatedEmbedderRunner] Processing system properties {}
> {code}
> As you can see it's reporting no properties passed. Digging into the Ant task
> code supports that the properties are not getting through, but from what I
> can see in the source there is no obvious reason. Possibly the code that
> loads the properties has a bug and is throwing an exception because it's
> try-catch silently swallows any errors.
--
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 inform
[jbehave-dev] [jira] Commented: (JBEHAVE-504) Ant task RunStoriesWithAnnotatedEmbedderRunner not passing system properties to embedder
[
http://jira.codehaus.org/browse/JBEHAVE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265561#action_265561
]
Mauro Talevi commented on JBEHAVE-504:
--
Derek, system properties (or other configurable properties) are all ignored
when running with AnnotatedEmbedderRunner, which by design gets the Embedder
configuration from the annotation @UsingEmbedder.
The system properties were missing in the @UsingEmbedder (now fixed in
JBEHAVE-506).
If you want to specify your configuration via Ant task, you can use a
ConfigurableEmbedder instance, e.g. JUnitStories.
> Ant task RunStoriesWithAnnotatedEmbedderRunner not passing system properties
> to embedder
>
>
> Key: JBEHAVE-504
> URL: http://jira.codehaus.org/browse/JBEHAVE-504
> Project: JBehave
> Issue Type: Bug
> Components: Ant Tasks
>Affects Versions: 3.3.2
> Environment: Ant
>Reporter: Derek Clarkson
>
> I'm trying to run JBehave from Ant using the following ant code:
> {code:xml}
> classname="org.jbehave.ant.RunStoriesWithAnnotatedEmbedderRunner"
> classpathref="integration.tests.classpath" />
> sourceDirectory="src/integration"
>
> systemProperties="java.awt.headless=true,web.project.dir=${build.integration.web.dir}"
>
> ignoreFailureInStories="true"
> ignoreFailureInView="false"
> generateViewAfterStories="true" />
> {code}
> At the momment I'm getting a class not found which the story embedder I've
> written starts up (doesn't happen from a junit run inside eclipse!).
> I think that it's running from the default directory because it appears that
> the systemProperties are not making it through to the embedder. Here's the
> log showing the startup:
> {code}
> run-bdd-tests:
> [runStoriesWithAnnotatedEmbedderRunner] Running stories with annotated
> embedder org.jbehave.core.junit.AnnotatedEmbedderRunner
> [runStoriesWithAnnotatedEmbedderRunner] Found class names :
> [au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder]
> [runStoriesWithAnnotatedEmbedderRunner] 2011-05-03 16:12:21,042 DEBUG
> [runStoriesWithAnnotatedEmbedderRunner] Processing system properties {}
> {code}
> As you can see it's reporting no properties passed. Digging into the Ant task
> code supports that the properties are not getting through, but from what I
> can see in the source there is no obvious reason. Possibly the code that
> loads the properties has a bug and is throwing an exception because it's
> try-catch silently swallows any errors.
--
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-506) Allow system properties to be specified for AnnotatedEmbedderRunner
[ http://jira.codehaus.org/browse/JBEHAVE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-506. -- Resolution: Fixed > Allow system properties to be specified for AnnotatedEmbedderRunner > --- > > Key: JBEHAVE-506 > URL: http://jira.codehaus.org/browse/JBEHAVE-506 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.4 > > > The AnnotatedEmbedderRunner is missing the specification of system properties > via the @UsingEmbedder. -- 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-505) Ant tasks running with incorrect classpath
[ http://jira.codehaus.org/browse/JBEHAVE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-505: - Affects Version/s: (was: web-3.2) 3.3.2 > Ant tasks running with incorrect classpath > -- > > Key: JBEHAVE-505 > URL: http://jira.codehaus.org/browse/JBEHAVE-505 > Project: JBehave > Issue Type: Bug > Components: Ant Tasks >Affects Versions: 3.3.2 >Reporter: Derek Clarkson > > I've been trying to make this work for hours now. It appears that the Ant > tasks run the Embedders with the classpath used to run Ant and that there is > no way to override this. This means I cannot run JBehave against the > classpaths used to build and test the application. > How do we specify a classpath for JBEhave's Ant tasks -- 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-505) Ant tasks running with incorrect classpath
[ http://jira.codehaus.org/browse/JBEHAVE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265562#action_265562 ] Mauro Talevi commented on JBEHAVE-505: -- Classloading in Ant is less than transparent, so ATM it uses the classloader used to load the task itself. Feel free to provide a patch that specifies the classloader in the "Ant way". > Ant tasks running with incorrect classpath > -- > > Key: JBEHAVE-505 > URL: http://jira.codehaus.org/browse/JBEHAVE-505 > Project: JBehave > Issue Type: Bug > Components: Ant Tasks >Affects Versions: 3.3.2 >Reporter: Derek Clarkson > > I've been trying to make this work for hours now. It appears that the Ant > tasks run the Embedders with the classpath used to run Ant and that there is > no way to override this. This means I cannot run JBehave against the > classpaths used to build and test the application. > How do we specify a classpath for JBEhave's Ant tasks -- 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-503) Add Ant script example in trader-maps to show how to generate story maps
[ http://jira.codehaus.org/browse/JBEHAVE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-503: - Component/s: (was: Core) Documentation Fix Version/s: 3.4 Assignee: Mauro Talevi Issue Type: Task (was: Bug) Summary: Add Ant script example in trader-maps to show how to generate story maps (was: maps.html not being generated) > Add Ant script example in trader-maps to show how to generate story maps > > > Key: JBEHAVE-503 > URL: http://jira.codehaus.org/browse/JBEHAVE-503 > Project: JBehave > Issue Type: Task > Components: Documentation >Affects Versions: 3.3.2 >Reporter: Derek Clarkson >Assignee: Mauro Talevi > Fix For: 3.4 > > > The generated reports include a link to a maps.html. But the file is not > generated. How do I turn it on or remove the link? -- 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-503) Add Ant script example in trader-maps to show how to generate story maps
[ http://jira.codehaus.org/browse/JBEHAVE-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-503. -- Resolution: Fixed See examples/trader-maps/build.xml for an example of how to configure story map generation > Add Ant script example in trader-maps to show how to generate story maps > > > Key: JBEHAVE-503 > URL: http://jira.codehaus.org/browse/JBEHAVE-503 > Project: JBehave > Issue Type: Task > Components: Documentation >Affects Versions: 3.3.2 >Reporter: Derek Clarkson >Assignee: Mauro Talevi > Fix For: 3.4 > > > The generated reports include a link to a maps.html. But the file is not > generated. How do I turn it on or remove the link? -- 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-497) Upgrade PicoContainer to 2.13.4
[ http://jira.codehaus.org/browse/JBEHAVE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-497. -- Resolution: Fixed > Upgrade PicoContainer to 2.13.4 > --- > > Key: JBEHAVE-497 > URL: http://jira.codehaus.org/browse/JBEHAVE-497 > Project: JBehave > Issue Type: Improvement > Components: Pico Support >Reporter: Paul Hammant >Assignee: Paul Hammant > Fix For: 3.4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-492) CandidateSteps instances should be created by StoryRunner context allowing for multi-threaded stateful steps logic
[ http://jira.codehaus.org/browse/JBEHAVE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-492 started by Mauro Talevi. > 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] Work started: (JBEHAVE-472) Improve state management of StoryRunner
[ http://jira.codehaus.org/browse/JBEHAVE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-472 started by Mauro Talevi. > Improve state management of StoryRunner > --- > > Key: JBEHAVE-472 > URL: http://jira.codehaus.org/browse/JBEHAVE-472 > Project: JBehave > Issue Type: Improvement > Components: Core >Affects Versions: 3.3 >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.4 > > > We need to improve the state management of the StoryRunner. > Currently after every set of steps run the state is reset and the scenario > @Before/@After steps are run separately from the normal steps, causing wierd > behaviours when there are failure in the @Before steps but not in the normal > steps. Examples of such a behaviour are the trader > failing_before_after.story and failing_before_stories.story. > A better and more intuitive state management should be in place, keeping > state in the run context. The state should be reset by default before each > scenario (to ensure backward compat) but will be shared between the > @Before/@After steps and the normal steps. > We should also have the option to not reset it before each scenario to allow > for failures in the @BeforeStory/Stories steps to propagate to the scenario > steps in the same run context. > Once a failing state in a given run context, the steps that follow will not > be performed, as customary with normal steps. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-497) Upgrade PicoContainer to 2.13.4
[ http://jira.codehaus.org/browse/JBEHAVE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-497: - Issue Type: Task (was: Improvement) > Upgrade PicoContainer to 2.13.4 > --- > > Key: JBEHAVE-497 > URL: http://jira.codehaus.org/browse/JBEHAVE-497 > Project: JBehave > Issue Type: Task > Components: Pico Support >Reporter: Paul Hammant >Assignee: Paul Hammant > Fix For: 3.4 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-2-32-g0eaeba7
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 0eaeba74b41bd5f3179aebc27aeb85bb99b29870 (commit)
via b84bf94e4430299a175a12f0b219f63f520c9c72 (commit)
from 9e558c053a740b74dde3bd00b6aab572417abd1c (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 0eaeba74b41bd5f3179aebc27aeb85bb99b29870
Author: Mauro Talevi
Date: Tue May 3 11:14:27 2011 +0200
Updated release notes.
commit b84bf94e4430299a175a12f0b219f63f520c9c72
Author: Mauro Talevi
Date: Tue May 3 11:06:36 2011 +0200
JBEHAVE-503: Added Ant script to generate story maps.
---
Summary of changes:
distribution/src/site/content/release-notes.html | 22 +--
.../{trader-annotations => trader-maps}/build.xml | 10
2 files changed, 24 insertions(+), 8 deletions(-)
copy examples/{trader-annotations => trader-maps}/build.xml (76%)
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-2-33-g02a7bc2
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 02a7bc29dd9aa88b1ccd65b8dd12a611d308b237 (commit) from 0eaeba74b41bd5f3179aebc27aeb85bb99b29870 (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 02a7bc29dd9aa88b1ccd65b8dd12a611d308b237 Author: Mauro Talevi Date: Tue May 3 11:42:02 2011 +0200 [maven-release-plugin] prepare release jbehave-3.4-beta-3 --- Summary of changes: archetypes/jbehave-groovy-archetype/pom.xml |2 +- archetypes/jbehave-simple-archetype/pom.xml |2 +- archetypes/jbehave-spring-archetype/pom.xml |2 +- archetypes/pom.xml |2 +- 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-odf/pom.xml |2 +- jbehave-pico/pom.xml|2 +- jbehave-spring/pom.xml |2 +- jbehave-weld/pom.xml|2 +- pom.xml |2 +- 16 files changed, 16 insertions(+), 16 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.4-beta-3, created. jbehave-3.4-beta-3
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.4-beta-3 has been created at 7faa40aaa3ad17e9a5f2dc920208aa74cd5f5f1b (tag) tagging 02a7bc29dd9aa88b1ccd65b8dd12a611d308b237 (commit) replaces jbehave-3.4-beta-2 tagged by Mauro Talevi on Tue May 3 11:42:08 2011 +0200 - Log - [maven-release-plugin] copy for tag jbehave-3.4-beta-3 Mauro Talevi (28): [maven-release-plugin] prepare for next development iteration Merge branch 'master' of github.com:maggandalf/jbehave-core JBEHAVE-472: Revert to using explicit scenario failures as criteria for report failure. JBEHAVE-492: Refactored Embedder and StoryRunner to use InjectableStepsFactory to create steps instances per thread in the runner context. If the InjectableStepsFactory is not set in the Embedder or ConfigurableEmbedder it will default to using the CandidateSteps provided and instantiate out of the story run context. Merge branch 'master' of ssh://git.codehaus.org/jbehave-core JBEHAVE-476: Updated doc page. JBEHAVE-496: Ignore null meta filter entries. JBEHAVE-492: Updated annotation builders to use steps factory by default. Behaviour controlled by @UsingEmbedder(stepsFactory=[true|false]) flag. Added CompositeStepsFactory to allow composition of steps factories, as typically used by DI containers. JBEHAVE-492: Ensured before and after stories steps use the same steps instances. JBEHAVE-492: As per Daniel Godfrey's suggestion, re-separated the Configuration concern from the InjectableStepsFactory, which returns to be solely focused on the creation of candidate steps. JBEHAVE-497: downgraded pico until artifact is on Maven Central. JBEHAVE-497: upgraded pico again. Merge branch 'master' of ssh://git.codehaus.org/jbehave-core JBEHAVE-499: Renamed maven goal to run-stories-with-annotated-embedder. Previous goal run-with-annotated-embedder kept for backward compat but deprecated. Fixed configuration of trader-annotations examples. Refactored noughtsandcrosses example to use uispec4j. More standard layout. Encapsulated all UI controls in single class WindowsControl. Updated build notes. JBEHAVE-500: AnnotatedEmbedderRunner now read from @RunWith annotation when running in CLI. JBEHAVE-500: Run both annotated embedders in the example. Removed file added by mistake. JBEHAVE-500: Removed obsolete property from docs. JBEHAVE-149: Applied patch from Bart De Neuter. JBEHAVE-501: Updated trader Ant script to show reports styling being generated. JBEHAVE-506: Added specification of system properties to @UsingEmbedder for use by AnnotatedEmbedderRunners. JBEHAVE-503: Added Ant script to generate story maps. Updated release notes. [maven-release-plugin] prepare release jbehave-3.4-beta-3 Paul Hammant (4): upgrade groovy JB-495 JBEHAVE-495: Upgraded groovy to 1.8 JBEHAVE-497 - upgrade pico upgrade pico dep again maggandalf (1): JBEHAVE-491 --- 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-3-1-g7b011ba
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 7b011baa4aab632e40dcaaae7d3f7790c8d397cc (commit) from 02a7bc29dd9aa88b1ccd65b8dd12a611d308b237 (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 7b011baa4aab632e40dcaaae7d3f7790c8d397cc Author: Mauro Talevi Date: Tue May 3 11:42:12 2011 +0200 [maven-release-plugin] prepare for next development iteration --- Summary of changes: archetypes/jbehave-groovy-archetype/pom.xml |2 +- archetypes/jbehave-simple-archetype/pom.xml |2 +- archetypes/jbehave-spring-archetype/pom.xml |2 +- archetypes/pom.xml |2 +- 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-odf/pom.xml |2 +- jbehave-pico/pom.xml|2 +- jbehave-spring/pom.xml |2 +- jbehave-weld/pom.xml|2 +- pom.xml |2 +- 16 files changed, 16 insertions(+), 16 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] Created: (JBEHAVE-507) unpack-view-resources goal requires resources to be in compile scope
unpack-view-resources goal requires resources to be in compile scope Key: JBEHAVE-507 URL: http://jira.codehaus.org/browse/JBEHAVE-507 Project: JBehave Issue Type: Improvement Components: Maven Plugin Affects Versions: web-3.3.1 Reporter: Caoilte O'Connor Priority: Minor Because I run JBehave in the test scope of the same project that it is testing I cannot use the compile scope for JBehave dependencies. However, the maven unpack-view-resources goal requires the resources to be in compile scope. This means that they get included in my final WAR. When I switch them to test scope the unpack-view-resources goal doesn't find them. I suppose the best fix would be to allow the unpack-view-resources goal to have its scope configured in the same way as the run-stories goals. -- 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-507) unpack-view-resources goal requires resources to be in compile scope
[
http://jira.codehaus.org/browse/JBEHAVE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265581#action_265581
]
Caoilte O'Connor commented on JBEHAVE-507:
--
problem dependencies:
org.jbehave.site
jbehave-site-resources
${jbehave.site.version}
zip
org.jbehave
jbehave-core
${jbehave.version}
resources
zip
> unpack-view-resources goal requires resources to be in compile scope
>
>
> Key: JBEHAVE-507
> URL: http://jira.codehaus.org/browse/JBEHAVE-507
> Project: JBehave
> Issue Type: Improvement
> Components: Maven Plugin
>Affects Versions: web-3.3.1
>Reporter: Caoilte O'Connor
>Priority: Minor
>
> Because I run JBehave in the test scope of the same project that it is
> testing I cannot use the compile scope for JBehave dependencies.
> However, the maven unpack-view-resources goal requires the resources to be in
> compile scope. This means that they get included in my final WAR.
> When I switch them to test scope the unpack-view-resources goal doesn't find
> them.
> I suppose the best fix would be to allow the unpack-view-resources goal to
> have its scope configured in the same way as the run-stories goals.
--
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-502) Add installation instructions to website documentation
[ http://jira.codehaus.org/browse/JBEHAVE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265591#action_265591 ] Derek Clarkson commented on JBEHAVE-502: @Christiano - Hi, I don't have a problem with maven and generally prefer it even though ant is generally speaking faster. The issue is that the company I work for is at the moment still using ant so I don't have the luxury of moving. There's not that many dependencies so it's not too much trouble. @Mauro - I think I found that. My issue is that the documentation assumed maven and didn't really cover any other situation. > Add installation instructions to website documentation > -- > > Key: JBEHAVE-502 > URL: http://jira.codehaus.org/browse/JBEHAVE-502 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Derek Clarkson > > I've been scouring the site for a couple of days trying to figure out what I > needed to install and where. I'm not using maven. The website doesn't give > any idea of how to setup JBehave when not in a maven environment. So I'm > having to do it by reverse engineering the maven pom. > The first problem was to trying and figure out what to download. The linked > download file is only of use in a maven world. So I had to start downloaded > by surfing the online repos. So I'd suggest that the raw jars and zips should > also be linked for download from the main site. > The second issue was what to unzip, etc and suggested directories. Again the > documentation takes a "it will just work" approach, which it doesn't. So > instructions are needed here to. -- 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-502) Add installation instructions to website documentation
[ http://jira.codehaus.org/browse/JBEHAVE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-502: - Fix Version/s: 3.4 We'll add more explicit instructions for Ant users in the dependencies page. > Add installation instructions to website documentation > -- > > Key: JBEHAVE-502 > URL: http://jira.codehaus.org/browse/JBEHAVE-502 > Project: JBehave > Issue Type: Improvement > Components: Core >Reporter: Derek Clarkson > Fix For: 3.4 > > > I've been scouring the site for a couple of days trying to figure out what I > needed to install and where. I'm not using maven. The website doesn't give > any idea of how to setup JBehave when not in a maven environment. So I'm > having to do it by reverse engineering the maven pom. > The first problem was to trying and figure out what to download. The linked > download file is only of use in a maven world. So I had to start downloaded > by surfing the online repos. So I'd suggest that the raw jars and zips should > also be linked for download from the main site. > The second issue was what to unzip, etc and suggested directories. Again the > documentation takes a "it will just work" approach, which it doesn't. So > instructions are needed here to. -- 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-502) Add installation instructions to website documentation
[ http://jira.codehaus.org/browse/JBEHAVE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-502: - Component/s: Documentation > Add installation instructions to website documentation > -- > > Key: JBEHAVE-502 > URL: http://jira.codehaus.org/browse/JBEHAVE-502 > Project: JBehave > Issue Type: Task > Components: Core, Documentation >Reporter: Derek Clarkson >Priority: Minor > Fix For: 3.4 > > > I've been scouring the site for a couple of days trying to figure out what I > needed to install and where. I'm not using maven. The website doesn't give > any idea of how to setup JBehave when not in a maven environment. So I'm > having to do it by reverse engineering the maven pom. > The first problem was to trying and figure out what to download. The linked > download file is only of use in a maven world. So I had to start downloaded > by surfing the online repos. So I'd suggest that the raw jars and zips should > also be linked for download from the main site. > The second issue was what to unzip, etc and suggested directories. Again the > documentation takes a "it will just work" approach, which it doesn't. So > instructions are needed here to. -- 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-502) Add installation instructions to website documentation
[ http://jira.codehaus.org/browse/JBEHAVE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-502: - Priority: Minor (was: Major) Issue Type: Task (was: Improvement) > Add installation instructions to website documentation > -- > > Key: JBEHAVE-502 > URL: http://jira.codehaus.org/browse/JBEHAVE-502 > Project: JBehave > Issue Type: Task > Components: Core, Documentation >Reporter: Derek Clarkson >Priority: Minor > Fix For: 3.4 > > > I've been scouring the site for a couple of days trying to figure out what I > needed to install and where. I'm not using maven. The website doesn't give > any idea of how to setup JBehave when not in a maven environment. So I'm > having to do it by reverse engineering the maven pom. > The first problem was to trying and figure out what to download. The linked > download file is only of use in a maven world. So I had to start downloaded > by surfing the online repos. So I'd suggest that the raw jars and zips should > also be linked for download from the main site. > The second issue was what to unzip, etc and suggested directories. Again the > documentation takes a "it will just work" approach, which it doesn't. So > instructions are needed here to. -- 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-3-2-g07c2b82
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 07c2b8278ff15d594a897f2a830e375828bd0894 (commit) from 7b011baa4aab632e40dcaaae7d3f7790c8d397cc (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 07c2b8278ff15d594a897f2a830e375828bd0894 Author: Mauro Talevi Date: Tue May 3 16:04:10 2011 +0100 JBEHAVE-502: Updated dependencies page to address the use case of Ant users without any dependency management tool. --- Summary of changes: distribution/src/site/content/dependencies.html | 13 - 1 files changed, 12 insertions(+), 1 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] Updated: (JBEHAVE-502) Add installation instructions to website documentation
[ http://jira.codehaus.org/browse/JBEHAVE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-502: - Component/s: (was: Core) > Add installation instructions to website documentation > -- > > Key: JBEHAVE-502 > URL: http://jira.codehaus.org/browse/JBEHAVE-502 > Project: JBehave > Issue Type: Task > Components: Documentation >Reporter: Derek Clarkson >Priority: Minor > Fix For: 3.4 > > > I've been scouring the site for a couple of days trying to figure out what I > needed to install and where. I'm not using maven. The website doesn't give > any idea of how to setup JBehave when not in a maven environment. So I'm > having to do it by reverse engineering the maven pom. > The first problem was to trying and figure out what to download. The linked > download file is only of use in a maven world. So I had to start downloaded > by surfing the online repos. So I'd suggest that the raw jars and zips should > also be linked for download from the main site. > The second issue was what to unzip, etc and suggested directories. Again the > documentation takes a "it will just work" approach, which it doesn't. So > instructions are needed here to. -- 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-502) Add installation instructions to website documentation
[ http://jira.codehaus.org/browse/JBEHAVE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-502. -- Resolution: Fixed > Add installation instructions to website documentation > -- > > Key: JBEHAVE-502 > URL: http://jira.codehaus.org/browse/JBEHAVE-502 > Project: JBehave > Issue Type: Task > Components: Documentation >Reporter: Derek Clarkson >Priority: Minor > Fix For: 3.4 > > > I've been scouring the site for a couple of days trying to figure out what I > needed to install and where. I'm not using maven. The website doesn't give > any idea of how to setup JBehave when not in a maven environment. So I'm > having to do it by reverse engineering the maven pom. > The first problem was to trying and figure out what to download. The linked > download file is only of use in a maven world. So I had to start downloaded > by surfing the online repos. So I'd suggest that the raw jars and zips should > also be linked for download from the main site. > The second issue was what to unzip, etc and suggested directories. Again the > documentation takes a "it will just work" approach, which it doesn't. So > instructions are needed here to. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.3.1-11-g9ed91fe
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-web". The branch, master has been updated via 9ed91fe628ec7c27fb6bfd9d043045d89c589f92 (commit) from 8d988e7de3cf60fde5bcf2f1d8a0809266c7e6d2 (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 9ed91fe628ec7c27fb6bfd9d043045d89c589f92 Author: Mauro Talevi Date: Tue May 3 18:03:55 2011 +0100 Cleanup --- Summary of changes: .../web/selenium/PerStoryWebDriverSteps.java |4 1 files changed, 0 insertions(+), 4 deletions(-) hooks/post-receive -- jbehave-web To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-3-3-g26caa4f
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 26caa4f9b8ca27a7092a1843aeec717c20dd878d (commit) from 07c2b8278ff15d594a897f2a830e375828bd0894 (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 26caa4f9b8ca27a7092a1843aeec717c20dd878d Author: Mauro Talevi Date: Tue May 3 20:19:01 2011 +0100 JBEHAVE-507: Extended dependency resolution of view resources artifacts to include test scope. --- Summary of changes: examples/pom.xml |2 ++ .../java/org/jbehave/mojo/UnpackViewResources.java |1 + 2 files changed, 3 insertions(+), 0 deletions(-) hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-507) unpack-view-resources goal requires resources to be in compile scope
[ http://jira.codehaus.org/browse/JBEHAVE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-507: - Affects Version/s: (was: web-3.3.1) Fix Version/s: 3.4 Assignee: Mauro Talevi > unpack-view-resources goal requires resources to be in compile scope > > > Key: JBEHAVE-507 > URL: http://jira.codehaus.org/browse/JBEHAVE-507 > Project: JBehave > Issue Type: Improvement > Components: Maven Plugin >Reporter: Caoilte O'Connor >Assignee: Mauro Talevi >Priority: Minor > Fix For: 3.4 > > > Because I run JBehave in the test scope of the same project that it is > testing I cannot use the compile scope for JBehave dependencies. > However, the maven unpack-view-resources goal requires the resources to be in > compile scope. This means that they get included in my final WAR. > When I switch them to test scope the unpack-view-resources goal doesn't find > them. > I suppose the best fix would be to allow the unpack-view-resources goal to > have its scope configured in the same way as the run-stories goals. -- 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-507) unpack-view-resources goal requires resources to be in compile scope
[ http://jira.codehaus.org/browse/JBEHAVE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-507. -- Resolution: Fixed Changed dependency resolution of Maven goal unpack-view-resources to include test scope. No additional configuration is required when using goal. Updated the examples view resources to be at test scope and all the examples modules (running either at compile or test scope) can access the view resources. > unpack-view-resources goal requires resources to be in compile scope > > > Key: JBEHAVE-507 > URL: http://jira.codehaus.org/browse/JBEHAVE-507 > Project: JBehave > Issue Type: Improvement > Components: Maven Plugin >Reporter: Caoilte O'Connor >Assignee: Mauro Talevi >Priority: Minor > Fix For: 3.4 > > > Because I run JBehave in the test scope of the same project that it is > testing I cannot use the compile scope for JBehave dependencies. > However, the maven unpack-view-resources goal requires the resources to be in > compile scope. This means that they get included in my final WAR. > When I switch them to test scope the unpack-view-resources goal doesn't find > them. > I suppose the best fix would be to allow the unpack-view-resources goal to > have its scope configured in the same way as the run-stories goals. -- 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-501) Report stying not being generated
[
http://jira.codehaus.org/browse/JBEHAVE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-501.
--
Resolution: Not A Bug
Fix Version/s: 3.4
> Report stying not being generated
> -
>
> Key: JBEHAVE-501
> URL: http://jira.codehaus.org/browse/JBEHAVE-501
> Project: JBehave
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.3.2
> Environment: Ant, Eclipse, JDK6
>Reporter: Derek Clarkson
> Fix For: 3.4
>
>
> I am using this report builder definition in a annotation setup as per the
> JBehave website documentation:
> public static class MyReportBuilder extends StoryReporterBuilder {
> public MyReportBuilder() {
> super();
>
> this.withCodeLocation(CodeLocations.codeLocationFromPath("build/publish/x"));
> this.withRelativeDirectory("story-reports");
> this.withDefaultFormats();
> this.withFormats(CONSOLE, HTML);
> }
> }
> The reports are being generated in the view directory, however there are no
> images, css or javascript being generated even though the html refers to
> them. I've scoured the web site documentation which suggests that they should
> be and tells you how to turn them off, but not what to do if they are not
> there.
--
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-504) Ant task RunStoriesWithAnnotatedEmbedderRunner not passing system properties to embedder
[
http://jira.codehaus.org/browse/JBEHAVE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi resolved JBEHAVE-504.
--
Resolution: Won't Fix
Fix Version/s: 3.4
> Ant task RunStoriesWithAnnotatedEmbedderRunner not passing system properties
> to embedder
>
>
> Key: JBEHAVE-504
> URL: http://jira.codehaus.org/browse/JBEHAVE-504
> Project: JBehave
> Issue Type: Bug
> Components: Ant Tasks
>Affects Versions: 3.3.2
> Environment: Ant
>Reporter: Derek Clarkson
> Fix For: 3.4
>
>
> I'm trying to run JBehave from Ant using the following ant code:
> {code:xml}
> classname="org.jbehave.ant.RunStoriesWithAnnotatedEmbedderRunner"
> classpathref="integration.tests.classpath" />
> sourceDirectory="src/integration"
>
> systemProperties="java.awt.headless=true,web.project.dir=${build.integration.web.dir}"
>
> ignoreFailureInStories="true"
> ignoreFailureInView="false"
> generateViewAfterStories="true" />
> {code}
> At the momment I'm getting a class not found which the story embedder I've
> written starts up (doesn't happen from a junit run inside eclipse!).
> I think that it's running from the default directory because it appears that
> the systemProperties are not making it through to the embedder. Here's the
> log showing the startup:
> {code}
> run-bdd-tests:
> [runStoriesWithAnnotatedEmbedderRunner] Running stories with annotated
> embedder org.jbehave.core.junit.AnnotatedEmbedderRunner
> [runStoriesWithAnnotatedEmbedderRunner] Found class names :
> [au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder]
> [runStoriesWithAnnotatedEmbedderRunner] 2011-05-03 16:12:21,042 DEBUG
> [runStoriesWithAnnotatedEmbedderRunner] Processing system properties {}
> {code}
> As you can see it's reporting no properties passed. Digging into the Ant task
> code supports that the properties are not getting through, but from what I
> can see in the source there is no obvious reason. Possibly the code that
> loads the properties has a bug and is throwing an exception because it's
> try-catch silently swallows any errors.
--
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-508) Statistics and curtained stack traces for "known errors".
Statistics and curtained stack traces for "known errors".
-
Key: JBEHAVE-508
URL: http://jira.codehaus.org/browse/JBEHAVE-508
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Paul Hammant
public void myStep {
throw new JBehaveKnownError("CORBA down");
}
If we threw the above from the middle of a step (subclasses RuntimeException or
AssertionError), JBehave could catch it, increment 1 for the Known error type
(simply the message payload), and list the step as failing without stack trace
in the outputs.
It relies on the known-error state being succinctly communicated to (or
determinable by) the steps class.
For web-apps, stack-traces in web-pages are a common development choice.
The stats aspect would be to report on the known error permutations for the run
in summary form
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.3.1-12-g5fcd575
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-web". The branch, master has been updated via 5fcd575ddeb72660160f01bc8e9cfda8aa30f6f6 (commit) from 9ed91fe628ec7c27fb6bfd9d043045d89c589f92 (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 5fcd575ddeb72660160f01bc8e9cfda8aa30f6f6 Author: Mauro Talevi Date: Tue May 3 23:55:13 2011 +0100 Updated to latest core version. --- Summary of changes: pom.xml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) hooks/post-receive -- jbehave-web To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-505) Ant tasks running with incorrect classpath
[ http://jira.codehaus.org/browse/JBEHAVE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265680#action_265680 ] Derek Clarkson commented on JBEHAVE-505: Normally would love to do so. But that means I'd have to do a full development cycle and ATM I don't have the bandwidth to take on another project. My thoughts are that without being able to set a classpath for the ant tasks, they might as well be retired. The reason is that every Ant project I've worked on is always about building and testing software. So running tests always means compiling code into directories, building a classpath with those directories and then handing it to the test runners. Without the ability to specific an ant class path property to work with, these ant tasks cannot work because the the classpath as used by ant doesn't contain any of the compiled code and never will. > Ant tasks running with incorrect classpath > -- > > Key: JBEHAVE-505 > URL: http://jira.codehaus.org/browse/JBEHAVE-505 > Project: JBehave > Issue Type: Bug > Components: Ant Tasks >Affects Versions: 3.3.2 >Reporter: Derek Clarkson > > I've been trying to make this work for hours now. It appears that the Ant > tasks run the Embedders with the classpath used to run Ant and that there is > no way to override this. This means I cannot run JBehave against the > classpaths used to build and test the application. > How do we specify a classpath for JBEhave's Ant tasks -- 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-504) Ant task RunStoriesWithAnnotatedEmbedderRunner not passing system properties to embedder
[
http://jira.codehaus.org/browse/JBEHAVE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265683#action_265683
]
Derek Clarkson commented on JBEHAVE-504:
Hmm, thats an issue for my code. I'm doing things with POJOs and annotations so
I'm not sure how I could setup a ConfigurableEmbedder without re-writing
everything.
The reason I was trying to set a property was that one of the classes used in
the test code needs to be passed a directory. Presently it's getting this from
a system property. It has a default that works fine inside eclipse, but when
running from ant I need to give it a different directory by setting a system
property.
> Ant task RunStoriesWithAnnotatedEmbedderRunner not passing system properties
> to embedder
>
>
> Key: JBEHAVE-504
> URL: http://jira.codehaus.org/browse/JBEHAVE-504
> Project: JBehave
> Issue Type: Bug
> Components: Ant Tasks
>Affects Versions: 3.3.2
> Environment: Ant
>Reporter: Derek Clarkson
> Fix For: 3.4
>
>
> I'm trying to run JBehave from Ant using the following ant code:
> {code:xml}
> classname="org.jbehave.ant.RunStoriesWithAnnotatedEmbedderRunner"
> classpathref="integration.tests.classpath" />
> sourceDirectory="src/integration"
>
> systemProperties="java.awt.headless=true,web.project.dir=${build.integration.web.dir}"
>
> ignoreFailureInStories="true"
> ignoreFailureInView="false"
> generateViewAfterStories="true" />
> {code}
> At the momment I'm getting a class not found which the story embedder I've
> written starts up (doesn't happen from a junit run inside eclipse!).
> I think that it's running from the default directory because it appears that
> the systemProperties are not making it through to the embedder. Here's the
> log showing the startup:
> {code}
> run-bdd-tests:
> [runStoriesWithAnnotatedEmbedderRunner] Running stories with annotated
> embedder org.jbehave.core.junit.AnnotatedEmbedderRunner
> [runStoriesWithAnnotatedEmbedderRunner] Found class names :
> [au.com.sensis.wireless.smsmanager.integration.bdd.stories.AnnotatedStoryEmbedder]
> [runStoriesWithAnnotatedEmbedderRunner] 2011-05-03 16:12:21,042 DEBUG
> [runStoriesWithAnnotatedEmbedderRunner] Processing system properties {}
> {code}
> As you can see it's reporting no properties passed. Digging into the Ant task
> code supports that the properties are not getting through, but from what I
> can see in the source there is no obvious reason. Possibly the code that
> loads the properties has a bug and is throwing an exception because it's
> try-catch silently swallows any errors.
--
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-501) Report stying not being generated
[
http://jira.codehaus.org/browse/JBEHAVE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265684#action_265684
]
Derek Clarkson commented on JBEHAVE-501:
Can I suggest that the template stuff be added to core and written out as part
of producing the reports. As it currently stands it's hard to find and not well
documented that users need to do this extra work to get it working.
> Report stying not being generated
> -
>
> Key: JBEHAVE-501
> URL: http://jira.codehaus.org/browse/JBEHAVE-501
> Project: JBehave
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.3.2
> Environment: Ant, Eclipse, JDK6
>Reporter: Derek Clarkson
> Fix For: 3.4
>
>
> I am using this report builder definition in a annotation setup as per the
> JBehave website documentation:
> public static class MyReportBuilder extends StoryReporterBuilder {
> public MyReportBuilder() {
> super();
>
> this.withCodeLocation(CodeLocations.codeLocationFromPath("build/publish/x"));
> this.withRelativeDirectory("story-reports");
> this.withDefaultFormats();
> this.withFormats(CONSOLE, HTML);
> }
> }
> The reports are being generated in the view directory, however there are no
> images, css or javascript being generated even though the html refers to
> them. I've scoured the web site documentation which suggests that they should
> be and tells you how to turn them off, but not what to do if they are not
> there.
--
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
