[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.0.3-32-g1946c1d

2010-10-16 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  1946c1d4c4445c15f047368ab554d73bc2184926 (commit)
  from  e9b0459d452dafd7d9e3119359dc153ea12b485d (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 1946c1d4c4445c15f047368ab554d73bc2184926
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date:   Sat Oct 16 13:13:37 2010 +0200

JBEHAVE-358:  Added StoryLanes to apply swimlanes paradigm to StoryMap view.

---

Summary of changes:
 .../java/org/jbehave/core/embedder/Embedder.java   |   11 ++--
 .../org/jbehave/core/embedder/StoryMapper.java |   12 +++--
 .../java/org/jbehave/core/model/StoryLanes.java|   53 
 .../main/java/org/jbehave/core/model/StoryMap.java |   25 +++--
 .../core/reporters/FreemarkerViewGenerator.java|   29 ++-
 .../src/main/resources/ftl/jbehave-story-maps.ftl  |   22 ++---
 .../src/main/resources/style/jbehave-reports.css   |2 +-
 .../core/embedder/StoryMapperBehaviour.java|3 +-
 8 files changed, 107 insertions(+), 50 deletions(-)
 create mode 100644 
jbehave-core/src/main/java/org/jbehave/core/model/StoryLanes.java


hooks/post-receive
-- 
jbehave-core

hr/
p
To unsubscribe from this list please visit:
/p
p
a 
href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a



[jbehave-scm] jbehave-web branch, master, updated. jbehave-web-3.1-beta-2-7-gc7510d4

2010-10-16 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-web.

The branch, master has been updated
   via  c7510d443527ecf2c2f3a3a9bf1e052520aba683 (commit)
  from  c375b7bc943a0abb1fab1f9a6b79982769bcad96 (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 c7510d443527ecf2c2f3a3a9bf1e052520aba683
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date:   Sat Oct 16 19:24:24 2010 +0200

Upgraded to latest Selenium 2 release.

---

Summary of changes:
 web-selenium/pom.xml |2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
jbehave-web

hr/
p
To unsubscribe from this list please visit:
/p
p
a 
href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a



[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.0.3-37-g792d383

2010-10-16 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  792d3837978f51e2c8ee10baf9aa6f6341221b4e (commit)
   via  d5c7008456a70e57f1b3e8479d1c57c8993d09f2 (commit)
   via  4019d1d26f4465412a9941bf372ab332b7d9aa46 (commit)
   via  aa9c820b6a4cc208058eb6fd7b3583bdf788f7c5 (commit)
  from  927a71b12655c7aa16d1d2e6763b770a1f4b0521 (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 792d3837978f51e2c8ee10baf9aa6f6341221b4e
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date:   Sat Oct 16 20:16:47 2010 +0200

JBEHAVE-362:  Refactored story reports to use the name resolver.

commit d5c7008456a70e57f1b3e8479d1c57c8993d09f2
Merge: 4019d1d26f4465412a9941bf372ab332b7d9aa46 
927a71b12655c7aa16d1d2e6763b770a1f4b0521
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date:   Sat Oct 16 19:32:52 2010 +0200

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

commit 4019d1d26f4465412a9941bf372ab332b7d9aa46
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date:   Sat Oct 16 19:19:24 2010 +0200

JBEHAVE-362:  Renamed implementation.

commit aa9c820b6a4cc208058eb6fd7b3583bdf788f7c5
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date:   Sat Oct 16 19:12:50 2010 +0200

JBEHAVE-362:  Added StoryNameResolver and UnderscoredToCapitalized 
implementation.  StoryMapper now uses it.

---

Summary of changes:
 .../org/jbehave/core/embedder/StoryMapper.java |7 +++--
 .../org/jbehave/core/io/StoryNameResolver.java |   12 ++
 .../jbehave/core/io/UnderscoredToCapitalized.java  |   21 ++
 .../core/reporters/FreemarkerViewGenerator.java|   23 +--
 .../ftl/jbehave-reports-index-with-totals.ftl  |8 +++---
 .../core/io/StoryNameResolverBehaviour.java|   19 
 6 files changed, 76 insertions(+), 14 deletions(-)
 create mode 100644 
jbehave-core/src/main/java/org/jbehave/core/io/StoryNameResolver.java
 create mode 100644 
jbehave-core/src/main/java/org/jbehave/core/io/UnderscoredToCapitalized.java
 create mode 100644 
jbehave-core/src/test/java/org/jbehave/core/io/StoryNameResolverBehaviour.java


hooks/post-receive
-- 
jbehave-core

hr/
p
To unsubscribe from this list please visit:
/p
p
a 
href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a



[jbehave-dev] [jira] Updated: (JBEHAVE-316) Define commom JAXB interfaces for systems to provide Features and its Stories and Scenarios to a JBehave runner.

2010-10-16 Thread Mauro Talevi (JIRA)

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

Mauro Talevi updated JBEHAVE-316:
-

Fix Version/s: (was: 3.1)
   3.2

 Define commom JAXB interfaces for systems to provide Features and its Stories 
 and Scenarios to a JBehave runner.
 

 Key: JBEHAVE-316
 URL: http://jira.codehaus.org/browse/JBEHAVE-316
 Project: JBehave
  Issue Type: New Feature
  Components: Core
Affects Versions: 3.0
Reporter: Cristiano GaviĆ£o
 Fix For: 3.2


 There are many systems where Stories could be writed, stored and mantained. 
 Some example are Confluence (using its excelent versioning handle), Rational 
 RSA, SparxSystems Enterprise Architect (both as scenarios inside 
 UseCases/Features UML elements).
 One way todo that integration would be Jbehave to provide commom classes 
 annotated with _javax.xml.bind.annotation.Xml*_ where developers could create 
 JAXB *Services* that will get data from whatevers system and serve Features, 
 its Stories and related Scenarios objects for JBehave as XML ou JSON.  

-- 
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] Assigned: (JBEHAVE-360) Improve tabular story report

2010-10-16 Thread Mauro Talevi (JIRA)

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

Mauro Talevi reassigned JBEHAVE-360:


Assignee: Mauro Talevi

 Improve tabular story report 
 -

 Key: JBEHAVE-360
 URL: http://jira.codehaus.org/browse/JBEHAVE-360
 Project: JBehave
  Issue Type: Improvement
  Components: Core
Affects Versions: 3.0.2
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Priority: Minor
 Fix For: 3.1


 Feedback from colleagues' first use of tabular story report introduced in 
 3.0.2 (JBEHAVE-339).
 - The layout is too dispersive, too much white space and table runs away out 
 of page
 - Unnecessary (or misleading) repetitions of column headers, such as 
 Successful and Failed
 - More difficult to spot failures, only numbers are colour-coded
 Suggestions include:
 - Have a top-level multi-column row with two headers, Scenarios and Steps.
 - Use logos (with hovering text) for Successful, Failed, Pending etc ...
 - Colour-code in red the story name in case of failure

-- 
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-358) Add Story Mapping with Swimlane view

2010-10-16 Thread Mauro Talevi (JIRA)

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

Mauro Talevi updated JBEHAVE-358:
-

Description: 
In order to get visibility of themes/epics
As a release planner
I want to be able to map stories by meta filters 

Using story maps allows us to group stories of cross-cutting concerns, using 
filters on meta info (JBEHAVE-220).

A swimlane view (with one lane per filter) would allow a clear and concise view.

  was:
In order to get visibility of themes/epics
As a release planner
I want to be able to view stories by theme/epic. 

Using story maps allows us to group stories of cross-cutting concerns.  
Themes/epics can be specified directly at story level using Meta info 
(JBEHAVE-220)


Summary: Add Story Mapping with Swimlane view  (was: Add Story 
Map/Theme views)

 Add Story Mapping with Swimlane view
 

 Key: JBEHAVE-358
 URL: http://jira.codehaus.org/browse/JBEHAVE-358
 Project: JBehave
  Issue Type: New Feature
  Components: Core
Reporter: Mauro Talevi
 Fix For: 3.1


 In order to get visibility of themes/epics
 As a release planner
 I want to be able to map stories by meta filters 
 Using story maps allows us to group stories of cross-cutting concerns, using 
 filters on meta info (JBEHAVE-220).
 A swimlane view (with one lane per filter) would allow a clear and concise 
 view.

-- 
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] Assigned: (JBEHAVE-362) Convert story name in report to human readable form

2010-10-16 Thread Mauro Talevi (JIRA)

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

Mauro Talevi reassigned JBEHAVE-362:


Assignee: Mauro Talevi

 Convert story name in report to human readable form
 ---

 Key: JBEHAVE-362
 URL: http://jira.codehaus.org/browse/JBEHAVE-362
 Project: JBehave
  Issue Type: Improvement
  Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Priority: Minor
 Fix For: 3.1


 Another good suggestion from feedback.  Convert:
 - trader_sells_stocks.story - Trader Sells Stocks

-- 
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-359) Allow filtering of stories and scenarios based on meta-info

2010-10-16 Thread Mauro Talevi (JIRA)

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

Mauro Talevi resolved JBEHAVE-359.
--

Resolution: Fixed

 Allow filtering of stories and scenarios based on meta-info
 ---

 Key: JBEHAVE-359
 URL: http://jira.codehaus.org/browse/JBEHAVE-359
 Project: JBehave
  Issue Type: New Feature
  Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
 Fix For: 3.1


 Once we have meta-info available in our stories and scenarios (JBEHAVE-220) 
 we can use this info to filter what is being run. 

-- 
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-328) Creation of a new parser to support the tracking of line numbers in error reporting.

2010-10-16 Thread Mauro Talevi (JIRA)

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

Mauro Talevi updated JBEHAVE-328:
-

Fix Version/s: (was: 3.1)
   3.2

 Creation of a new parser to support the tracking of line numbers in error 
 reporting.
 

 Key: JBEHAVE-328
 URL: http://jira.codehaus.org/browse/JBEHAVE-328
 Project: JBehave
  Issue Type: Improvement
  Components: Core
Affects Versions: 3.1
Reporter: Mike Neeve
 Fix For: 3.2

 Attachments: jbehave-core.patch


 Attached is a patch for JBehave.
 The main change is the addition of a new parser. Its based on Eclipse JFace, 
 which means we can track line numbers in error reporting. It can also be 
 re-used for syntax highlighting in an Eclipse editor. JFace requires some 
 Eclipse libraries, so these are new dependencies which still work even though 
 we're not running in an OSGi container. The parser is also very fast compared 
 to the current regex-based parser - the longest running test was 25s for the 
 previous parser, and now its just 0.5s.
 In ScenarioParserBehaviour we've written some tests for the default 
 configuration of JUnitScenario. They fail with the current parser but pass 
 with the new one which is able to throw a new ParseException for each type of 
 problem.
 We've added one test to CandidateStepBehaviour.java that currently fails. 
 Doug tried fixing it by changing the ExamplesTable to be backed by a 
 LinkedHashMap which means that the arguments are automatically in the correct 
 order. But this did not work for other examples and couldn't figure out how 
 to make it work, so the test is currently broken. We'd need help to fix this.
 Further proposed changes would improve the detection of problems such as:
 - not having enough columns in the examples section to cover all the required 
 variables
 - having more columns than required in the examples section
 - checking the order of statements e.g. ensure a When comes after a Given
 - allowing boolean's for parameters
 The first two are quite difficult as it involves a good knowledge of the 
 CandidateStep class.

-- 
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.0.3-39-g59f3db6

2010-10-16 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  59f3db60d7f75e30e0651cd6c6164ee159078e0b (commit)
  from  c753727ffa990c7dfb9cdb5bf0b7a60d9ff72afe (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 59f3db60d7f75e30e0651cd6c6164ee159078e0b
Author: Mauro Talevi mauro.tal...@aquilonia.org
Date:   Sat Oct 16 21:54:31 2010 +0200

JBEHAVE-358:  Styling.

---

Summary of changes:
 .../src/main/resources/ftl/jbehave-story-maps.ftl  |4 ++--
 .../src/main/resources/style/jbehave-reports.css   |6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)


hooks/post-receive
-- 
jbehave-core

hr/
p
To unsubscribe from this list please visit:
/p
p
a 
href=http://xircles.codehaus.org/manage_email;http://xircles.codehaus.org/manage_email/a