[jbehave-scm] [scm-core][1/1] JBEHAVE-917: Allow generic lists.

2013-05-26 Thread Mauro Talevi
commit c107eea86c40ce4d2b327a2f873e923e306861b3 Author: Mauro Talevi AuthorDate: Sun, 26 May 2013 13:23:47 +0200 Commit: Mauro Talevi CommitDate: Sun, 26 May 2013 13:23:47 +0200 JBEHAVE-917: Allow generic lists. diff --git a/jbehave-core/src/main/java/org/jbehave/core/steps/Instan

[jbehave-scm] [scm-core/jbehave-4.x][1/1] JBEHAVE-917: Allow generic lists.

2013-05-26 Thread Mauro Talevi
commit 6e50ef8d8cf00156af23a116c9f076ef833c1114 Author: Mauro Talevi AuthorDate: Sun, 26 May 2013 13:23:47 +0200 Commit: Mauro Talevi CommitDate: Sun, 26 May 2013 13:38:53 +0200 JBEHAVE-917: Allow generic lists. diff --git a/jbehave-core/src/main/java/org/jbehave/core/steps/Instan

[jbehave-dev] [jira] (JBEHAVE-917) Use more flexible "Consumer extends" for list of step instances.

2013-05-26 Thread Mauro Talevi (JIRA)
Mauro Ta

RE: [jbehave-dev] Submit reports to database

2013-05-26 Thread joao machado
Hi Mauro and JBehave devs, first of all thank you for your prompt reply. Your suggestion is really great for our purpose because, as you write in the previous e-mail, we want to submit stories execution status to the Rally (rallydev.com) database and also create the HTML reports in the continu

[jbehave-dev] [jira] (JBEHAVE-902) Improve extensibility of core elements

2013-05-26 Thread Mauro Talevi (JIRA)
Mauro Talevi

Re: [jbehave-dev] Submit reports to database

2013-05-26 Thread Mauro Talevi
Hi, if your need is to interface with Rally, I'd opt to have a jbehave-rally module that deals with all the specifics of rally, in particular the db schema. Then we can also add other elements of this interaction as needed, e.g. a Rally specifc configuration extension that makes it easy for

[jbehave-dev] [jira] (JBEHAVE-902) Improve extensibility of core elements

2013-05-26 Thread Mauro Talevi (JIRA)
Mauro Ta

RE: [jbehave-dev] Submit reports to database

2013-05-26 Thread joao machado
Hi again, We already have jbehave-rally module but we need something like PerformableTree to access Story information and the ability to perform individual stories concurrently is definitely plus. Should I use this module in my overridden run() after the execution of generateReports

[jbehave-dev] [jira] (JBEHAVE-918) Allow specification of include/exclude filters as CSV in StoryFinder

2013-05-26 Thread Mauro Talevi (JIRA)
Mauro Tal

[jbehave-dev] [jira] (JBEHAVE-918) Allow specification of include/exclude filters as CSV in StoryFinder

2013-05-26 Thread Mauro Talevi (JIRA)
Mauro Ta

Re: [jbehave-dev] Submit reports to database

2013-05-26 Thread Mauro Talevi
You can access the PerformableRoot of the tree via Embedder.storyManager().performableRoot(). It will be generated during the generateReportsView() method using the view generator configured via: Configuration.useViewGenerator(ViewGenerator). So there only one view generator for given run.

[jbehave-dev] [jira] (JBEHAVE-919) Rename example modules

2013-05-26 Thread Mauro Talevi (JIRA)
Mauro Tal

RE: [jbehave-dev] Submit reports to database

2013-05-26 Thread joao machado
I misunderstand the purpose of the ViewGenerator interface. The main purpose of the interface is file-based reports and was I thinking of a more generic generator for reporting purposes (file-based, database, etc). I'll let you know the updates on this issue. Date: Sun, 26 May 2013 18:09:46 +02