Paul Hammant (JIRA | 2 May 04:14 2011

[jira] Created: (JBEHAVE-497) Upgrade PicoContainer to 2.13.4

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

Konstantin Ilinov (JIRA | 2 May 06:21 2011

[jira] Commented: (JBEHAVE-233) Eclipse plugin for navigating between textual and code steps


    [
http://jira.codehaus.org/browse/JBEHAVE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265405#action_265405
] 

Konstantin Ilinov commented on JBEHAVE-233:
-------------------------------------------

Hi Szczepan - givwenzen looks interesting, would be good to see smth similar for JBehave as JBehave already
has plain text scenarios (rather than DomainSteps/Step etc. annotations). I am pretty sure JBehave
community would like better Eclipse (and other IDEs) integration. 

> Eclipse plugin for navigating between textual and code steps
> ------------------------------------------------------------
>
>                 Key: JBEHAVE-233
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-233
>             Project: JBehave
>          Issue Type: New Feature
>            Reporter: Jonathan Ross
>
> As an avid user of jBehave, I find maintaining steps very laborious, so I would like an eclipse plugin with:
> * support for opening declarations of steps from the scenario files
> * support for finding usages of steps in scenario files from the declaration
> * support for opening the declaration of failed steps when running junit
> Nice to have:
> * refactoring support: when editing the annotations, scenarios using the step get rewritten

--

-- 
This message is automatically generated by JIRA.
(Continue reading)

Derek Clarkson (JIRA | 2 May 08:16 2011

[jira] Created: (JBEHAVE-498) withRelativeDirectory appears to be broken

withRelativeDirectory appears to be broken
------------------------------------------

                 Key: JBEHAVE-498
                 URL: http://jira.codehaus.org/browse/JBEHAVE-498
             Project: JBehave
          Issue Type: Bug
          Components: Core
    Affects Versions: web-3.3
         Environment: Linux. Jdk6
            Reporter: Derek Clarkson

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)
(Continue reading)

Mauro Talevi (JIRA | 2 May 11:11 2011

[jira] Commented: (JBEHAVE-498) withRelativeDirectory appears to be broken


    [
http://jira.codehaus.org/browse/JBEHAVE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265426#action_265426
] 

Mauro Talevi commented on JBEHAVE-498:
--------------------------------------

The relativeDirectory is the directory where the JBehave reporting outputs are written to (defaults to
"jbehave"), relative to the story builder code location (defaults to
CodeLocations.codeLocationFromPath("target/classes")). 

If you change the relative directory and you're not using the Maven standard layout, you'll probably need
to set the code location accordingly, e.g. CodeLocations.codeLocationFromPath("build/publish")
and withRelativeDirectory("story-reports"), or combinations thereof.  

You could also try seting the code location from the JUnitStories class:  CodeLocations.codeLocationFromClass(this.getClass());

> withRelativeDirectory appears to be broken
> ------------------------------------------
>
>                 Key: JBEHAVE-498
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-498
>             Project: JBehave
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: web-3.3
>         Environment: Linux. Jdk6
>            Reporter: Derek Clarkson
>
(Continue reading)

Mauro Talevi (JIRA | 2 May 21:52 2011

[jira] Created: (JBEHAVE-499) Rename run-with-annotated-embedder goal to run-stories-with-annotated-embedder

Rename run-with-annotated-embedder goal to run-stories-with-annotated-embedder
------------------------------------------------------------------------------

                 Key: JBEHAVE-499
                 URL: http://jira.codehaus.org/browse/JBEHAVE-499
             Project: JBehave
          Issue Type: Improvement
          Components: Maven Plugin
            Reporter: Mauro Talevi
            Assignee: Mauro Talevi
            Priority: Minor
             Fix For: 3.4

The goal name is inconsistent with the other goal names.  For backward compat, we can keep the previous goal name.

--

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

Mauro Talevi (JIRA | 2 May 22:26 2011

[jira] Resolved: (JBEHAVE-499) Rename run-with-annotated-embedder goal to run-stories-with-annotated-embedder


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

Mauro Talevi resolved JBEHAVE-499.
----------------------------------

    Resolution: Fixed

> Rename run-with-annotated-embedder goal to run-stories-with-annotated-embedder
> ------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-499
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-499
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Maven Plugin
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>            Priority: Minor
>             Fix For: 3.4
>
>
> The goal name is inconsistent with the other goal names.  For backward compat, we can keep the previous goal name.

--

-- 
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
-
(Continue reading)

Bart De Neuter (JIRA | 3 May 00:04 2011

[jira] Updated: (JBEHAVE-149) Support loading of stories from ODT format


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

Bart De Neuter updated JBEHAVE-149:
-----------------------------------

    Attachment: jbehave-odf-with-table.zip

Mauro,

I made some adjustments in order to use a real odt table in the text document. In that sense you can specify the
example table with a nice layout. I attached the changes I made to your code.

> Support loading of stories from ODT format
> ------------------------------------------
>
>                 Key: JBEHAVE-149
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-149
>             Project: JBehave
>          Issue Type: New Feature
>          Components: ODF Support
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 3.4
>
>         Attachments: jbehave-odf-with-table.zip
>
>
> As a BA I want to be able to write my story in a ODT format
(Continue reading)

Mauro Talevi (JIRA | 3 May 01:05 2011

[jira] Created: (JBEHAVE-500) Annotated Embedder Runner class should be read from annotation when running in CLI

Annotated Embedder Runner class should be read from annotation when running in CLI
----------------------------------------------------------------------------------

                 Key: JBEHAVE-500
                 URL: http://jira.codehaus.org/browse/JBEHAVE-500
             Project: JBehave
          Issue Type: Improvement
          Components: Maven Plugin
            Reporter: Mauro Talevi
            Assignee: Mauro Talevi
            Priority: Minor
             Fix For: 3.4

As noted by Cristiano Gavião, the Ant and Maven configuration of the AnnotatedEmbedderRunner class is
redundant as it can be read from the annotated value.

--

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

Mauro Talevi (JIRA | 3 May 01:10 2011

[jira] Resolved: (JBEHAVE-500) Annotated Embedder Runner class should be read from annotation when running in CLI


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

Mauro Talevi resolved JBEHAVE-500.
----------------------------------

    Resolution: Fixed

> Annotated Embedder Runner class should be read from annotation when running in CLI
> ----------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-500
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-500
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Maven Plugin
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>            Priority: Minor
>             Fix For: 3.4
>
>
> As noted by Cristiano Gavião, the Ant and Maven configuration of the AnnotatedEmbedderRunner class is
redundant as it can be read from the annotated value.

--

-- 
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
(Continue reading)

Mauro Talevi (JIRA | 3 May 01:27 2011

[jira] Commented: (JBEHAVE-149) Support loading of stories from ODT format


    [
http://jira.codehaus.org/browse/JBEHAVE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265516#action_265516
] 

Mauro Talevi commented on JBEHAVE-149:
--------------------------------------

Thanks, Bart.  Patch applied.

> Support loading of stories from ODT format
> ------------------------------------------
>
>                 Key: JBEHAVE-149
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-149
>             Project: JBehave
>          Issue Type: New Feature
>          Components: ODF Support
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 3.4
>
>         Attachments: jbehave-odf-with-table.zip
>
>
> As a BA I want to be able to write my story in a ODT format

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)


Gmane