[jbehave-scm] [1256] trunk/core/distribution/src/site/content: Added documentation, providing followup trails from one page to another.

Sat, 19 Sep 2009 10:49:05 -0700

Title: [1256] trunk/core/distribution/src/site/content: Added documentation, providing followup trails from one page to another.

Diff

Added: trunk/core/distribution/src/site/content/bdd-concepts.html (0 => 1256)

--- trunk/core/distribution/src/site/content/bdd-concepts.html	                        (rev 0)
+++ trunk/core/distribution/src/site/content/bdd-concepts.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -0,0 +1,32 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<title>BDD Concepts</title>
+</head>
+
+<body>
+
+<h2>BDD Concepts</h2>
+
+<p>BDD revolves around the concept of a <b>Scenario</b>, which at
+its core comprises of a number of executed Steps. The <b>Steps</b> can
+be of three types:</p>
+<ul>
+    <li><b>Given</b> represents a precondition to an event</li>
+    <li><b>When</b> represents an event</li>
+    <li><b>Then</b> represents an outcome of the event</li>
+</ul>
+<p>A <b>Story</b> or a <b>Feature</b>, in turn, comprises of one of
+more <b>Scenarios</b>.</p>
+
+<h2>Next?</h2>
+
+<span class="followup">Learn about the full <a
+    href="" JBehave supports.</span>
+
+<div class="clear">
+<hr />
+</div>
+
+</body>
+</html>

Added: trunk/core/distribution/src/site/content/bdd-resources.html (0 => 1256)

--- trunk/core/distribution/src/site/content/bdd-resources.html	                        (rev 0)
+++ trunk/core/distribution/src/site/content/bdd-resources.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -0,0 +1,21 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<title>BDD Resources</title>
+</head>
+
+<body>
+
+<h2>BDD Resources</h2>
+
+<p>You can find out more about behaviour-driven development on <a
+    href=""
+<p>Newcomers are encouraged to start from <a
+    href="" BDD</a>.</p>
+
+<div class="clear">
+<hr />
+</div>
+
+</body>
+</html>

Added: trunk/core/distribution/src/site/content/configuring-scenarios.html (0 => 1256)

--- trunk/core/distribution/src/site/content/configuring-scenarios.html	                        (rev 0)
+++ trunk/core/distribution/src/site/content/configuring-scenarios.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -0,0 +1,51 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<title>Configuring Scenarios</title>
+</head>
+
+<body>
+
+<h2>Configuring Scenarios</h2>
+
+<p>JBehave was designed to be highly configurable but to provide
+default behaviour for the most useful configuration. <a
+    href=""
+is the main interface for configuring all the components of a scenario.</p>
+
+<p>JBehave provides two implementations:</p>
+<p><a
+    href=""
+provides default configuration that most user will find appropriate</p>
+<p><a
+    href=""
+overrides default configuration via system properties</p>
+
+
+<h2>Configuring Steps</h2>
+
+<p>Steps can also be configured to a high degree via the <a
+    href=""
+Among the elements that can be configured are:</p>
+<p><a
+    href=""
+defaults to <a
+    href=""
+<p><a
+    href=""
+defaults to <a
+    href=""
+useful to either debug the step matching or to describe the steps being
+performed to some output</p>
+<p><a
+    href=""
+facade for collecting user-defined <a
+    href=""
+
+
+<div class="clear">
+<hr />
+</div>
+
+</body>
+</html>

Modified: trunk/core/distribution/src/site/content/developing-scenarios.html (1255 => 1256)

--- trunk/core/distribution/src/site/content/developing-scenarios.html	2009-09-19 14:15:10 UTC (rev 1255)
+++ trunk/core/distribution/src/site/content/developing-scenarios.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -6,50 +6,32 @@
 
 <body>
 
-<h2>Writing Text Scenarios</h2>
+<h2>Writing Textual Scenarios</h2>
 
-<p>We encourage users to start from writing your scenarios in a
-non-Java format, e.g. in simple text: <textarea
+<p>BDD encourages you to start defining the scenarios that express
+the desired behaviour in a textual format, e.g.: <textarea
     class="xml:nogutter:nocontrols" name="code">
     Given a stock of symbol STK1 and a threshold of 10.0
     When the stock is traded at 5.0
     Then the alert status should be OFF
     When the stock is traded at 11.0
     Then the alert status should be ON
-</textarea> and to give a name that is expressive, i.e. <code>status_alert_can_be_activated.scenario</code>.
-This scenario will map to a Java file <code>StatusAlertCanBeActivated.java</code>
-in same package.</p>
-
-<h2>Writing Java Scenarios</h2>
-
-<p>The contract for a user-defined Java scenario is the following:</p>
-<p>Must extend an instance of a <a
-    href=""
-such as <a href=""
+</textarea>. The textual scenario should use the language of the business domain
+and shield away as much as possible the details of the technical
+implementation. Also, it should be given a name that is expressive of
+the functionality that is being verified, i.e. <b>trader_is_alerted_of_status.scenario</b>.
 </p>
-<p>Must provide a default constructor and a constructor with a
-ClassLoader parameter, e.g.: <textarea class="java:nogutter:nocontrols"
-    name="code">
-   public class StatusAlertCanBeActivated extends JUnitScenario {
+<p>The scenario should use a syntax compatible with the <a
+    href=""
 
-    public StatusAlertCanBeActivated() {
-        this(Thread.currentThread().getContextClassLoader());
-    }
+<h2>Mapping Textual Scenarios to Java</h2>
 
-    public StatusAlertCanBeActivated(final ClassLoader classLoader) {
-        super(new MostUsefulConfiguration() {
-            public ScenarioDefiner forDefiningScenarios() {
-                return new ClasspathScenarioDefiner(new UnderscoredCamelCaseResolver(".scenario"), 
-                            new PatternScenarioParser(new PropertyBasedConfiguration()), classLoader);
-            }
-        }, new TraderSteps());
-    }
-
-}
-</textarea></p>
-<p>Must inject an instance of <a
-    href=""
-e.g.: <textarea class="java:nogutter:nocontrols" name="code">
+<p>JBehave maps textual steps to Java method via a <a
+    href=""
+class. The scenario writer need only extends the default implementation
+<a href=""
+and provide annotated method that match the textual steps by regex
+patterns: <textarea class="java:nogutter:nocontrols" name="code">
    public class TraderSteps extends Steps {
 
     private Stock stock;
@@ -71,44 +53,56 @@
 
 }
 </textarea></p>
-</p>
 
-<h2>Configuring Scenarios</h2>
+<h2>Running Scenarios</h2>
 
-<p>JBehave was designed to be highly configurable but to provide
-default behaviour for the most useful configuration. <a
-    href=""
-is the main interface for configuring all the components of a scenario.
-JBehave provides two implementations:
-<p><a
-    href=""
-provides default configuration that most user will find appropriate</p>
-<p><a
-    href=""
-overrides default configuration via system properties</p>
+<p>In JBehave Core scenarios can be run in an automated way via a
+one-to-one mapping to Java files. The mechanism via which the textual
+scenarios are resolved is determined by the implementation of the <a
+    href=""
+In our example, we need to create a file <code>TraderIsAletedOfStatus.java</code>,
+which maps to out textual scenario in same package.</p>
+
+<p>The contract for a user-defined Java scenario is the following:</p>
+<p>Must extend an instance of a <a
+    href=""
+such as <a href=""
 </p>
+<p>Must provide a default constructor.</p>
+<p>(Only when running via Maven) Must provide an additional
+constructor with a ClassLoader parameter.</p>
 
-<h2>Configuring Steps</h2>
+<p>Thus in our case the example Scenario would look like: <textarea
+    class="java:nogutter:nocontrols" name="code">
+   public class TraderIsAletedOfStatus extends JUnitScenario {
 
-<p>Steps can also be configured to a high degree via the <a
-    href=""
-Among the elements that can be configured are:
-<p><a
-    href=""
-defaults to <a
-    href=""
-<p><a
-    href=""
-defaults to <a
-    href=""
-useful to either debug the step matching or to describe the steps being
-performed to some output</p>
-<p><a
-    href=""
-facade for collecting user-defined <a
-    href=""
+    public TraderIsAletedOfStatus() {
+        this(Thread.currentThread().getContextClassLoader());
+    }
 
-</p>
+    public TraderIsAletedOfStatus(final ClassLoader classLoader) {
+        super(new MostUsefulConfiguration() {
+            public ScenarioDefiner forDefiningScenarios() {
+                return new ClasspathScenarioDefiner(new UnderscoredCamelCaseResolver(".scenario"), 
+                            new PatternScenarioParser(new PropertyBasedConfiguration()), classLoader);
+            }
+        }, new TraderSteps());
+    }
+
+}
+</textarea></p>
+<p>Here we are configuring our textual scenario files to end with
+extension <b>.scenario</b>, by overriding the default behaviour of <a
+    href=""
+which has no extension.</p>
+
+<h2>Next?</h2>
+
+<span class="followup">The <a href=""
+Scenarios</a> page will go into more configuration details and <a
+    href="" Scenarios</a> into the
+different ways to run scenarios.</span>
+
 <div class="clear">
 <hr />
 </div>

Modified: trunk/core/distribution/src/site/content/getting-started.html (1255 => 1256)

--- trunk/core/distribution/src/site/content/getting-started.html	2009-09-19 14:15:10 UTC (rev 1255)
+++ trunk/core/distribution/src/site/content/getting-started.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -80,10 +80,13 @@
 
       }
   </textarea></p>
-<p>Run your new scenario as JUnit test.</p>
-<p>Check out the working <a
+<p>4. Run your new scenario as JUnit test.</p>
+
+<h2>Looking for more examples?</h2>
+
+<span class="followup">JBehave has a number of working <a
     href=""
-in the source repository.</p>
+in the source repository, which illustrate its features.</span>
 
 </body>
 </html>
\ No newline at end of file

Added: trunk/core/distribution/src/site/content/grammar.html (0 => 1256)

--- trunk/core/distribution/src/site/content/grammar.html	                        (rev 0)
+++ trunk/core/distribution/src/site/content/grammar.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -0,0 +1,95 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<title>Grammar</title>
+</head>
+
+<body>
+
+<h2>EBNF Grammar</h2>
+
+<p>Below is a detailed outlay of the grammar JBehave understands.  It is expressed in <a href=""
+<textarea
+    class="xml:nogutter:nocontrols" name="code">
+; JBehave Grammar expressed in EBNF (http://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_Form)
+
+; The story or feature is a collection of scenarios
+Story := Scenario+
+
+; The scenario is identified by keyword "Scenario:" (or equivalent in I18n-ed locale),
+; which is optional in the case of a single scenario.  
+; It can optionally be followed by a description, which is expressed by any sequence of words
+; that must not contain any keywords
+; Then follow the Steps 
+; Finally the Examples table, which if present will execute the scenario for as many table rows present
+Scenario := "Scenario:"? Description? GivenScenarios? Step+ Examples?
+
+; The scenario description
+Description := (Word Space?)* 
+
+; The word is any sequence of non-space characters that does not match a KeyWord
+Word := NonSpaceCharacter* ; TODO express "!Keyword"
+
+; The space between words
+Space := " "
+
+; Any non-space character
+NonSpaceCharacter := [.] ; TODO express "!Space"
+
+; The keywords which are reserved (or equivalent in I18n-ed locale)
+KeyWord := "Scenario:" | "GivenScenarios:" | "Given" | "When" | "Then" | "And" 
+
+; The comma-separated list of scenario resources that specify the scenarios to be run before the scenario steps
+GivenScenarios:= "GivenScenarios:" (ScenarioResourcePath ','?)+
+
+; The scenario resource path  
+ScenarioResourcePath := PathCharacter+
+
+; The characters allowed in a scenario resource path
+PathCharacter := "/" | "." | "_" | Letter | Digit 
+
+; The letter characters
+Letter := [A-Z] | [a-z]
+
+; The digit characters
+Digit := [0-9]
+
+; The scenario step is a step starting work followed by any number of characters
+Step := StepStartingWord StepContent
+
+; The step starting words (or equivalent in I18n-ed locale)
+StepStartingWord :== ("Given" | "When" | "Then" | "And" ) 
+
+; The step content is any sequence of characters that do not match a step starting word
+StepContent := StepCharacter+ ; TODO express "!StepStartingWord"
+
+; All characters are allowed in a scenario step content, including newlines
+StepCharacter := [.]
+
+; The examples table
+Examples := "Examples:" Table
+
+; The table comprises of a header row and data rows
+Table := TableHeader TableRow+
+
+; The table header contains the column names, separated by TableColumnSeparator
+TableHeader := ((TableColumnSeparator TableCharacter+)+ TableColumnSeparator  Newline
+
+; The table row contains the column values, separated by TableColumnSeparator
+TableRow := ((TableColumnSeparator TableCharacter+)+ TableColumnSeparator  Newline
+
+; The table column separator
+TableColumnSeparator := "|"
+
+; The table character can be any character, expect for TableColumnSeparator and Newline
+TableCharacter := [.] ; TODO express !TableColumnSeparator and !Newline
+
+; The new line character
+Newline := "\n"
+</textarea>
+<div class="clear">
+<hr />
+</div>
+
+</body>
+</html>

Added: trunk/core/distribution/src/site/content/i18n.html (0 => 1256)

--- trunk/core/distribution/src/site/content/i18n.html	                        (rev 0)
+++ trunk/core/distribution/src/site/content/i18n.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -0,0 +1,121 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<title>Using your language</title>
+</head>
+
+<body>
+
+<h2>Writing Scenarios in your Language</h2>
+
+<p>Good and effective communication is key to BDD. Therefore,
+writing scenarios in the <a href=""
+spoken by the business users is essential. And even though the patterns
+used to match the scenario steps to Java methods can be written in any
+language, the <a
+    href=""
+still need to be expressed in different languages.</p>
+
+<p>JBehave allows the internationalisation (I18N) of keywords by by
+Java <a
+    href=""
+thus allowing the scenarios to be written in any language. All is needed
+to configure the use of <a
+    href=""
+for a given Locale. Each locale has a separate keywords properties file.
+E.g. for Italian locale, the file <b>keywords_it.properties</b> is: <textarea
+    class="properties:nogutter:nocontrols" name="code">
+Scenario=Scenario:
+GivenScenarios=Dati gli scenari:
+ExamplesTable=Esempi:
+ExamplesTableRow=Esempio:
+Given=Dato che
+When=Quando
+Then=Allora
+And=E
+Pending=PENDENTE
+NotPerformed=NON ESEGUITO
+Failed=FALLITO
+</textarea></p>
+<p>We need to configure the use of the I18N-ed keywords in the <a
+    href=""
+e.g.: <textarea class="java:nogutter:nocontrols" name="code">
+   public class ItTraderScenario extends JUnitScenario {
+
+	public ItTraderScenario() {
+		this(Thread.currentThread().getContextClassLoader());
+	}
+
+	public ItTraderScenario(final ClassLoader classLoader) {
+		super(new PropertyBasedConfiguration() {
+			@Override
+			public KeyWords keywords() {
+				// use Italian for keywords
+				return new I18nKeyWords(new Locale("it"));
+			}
+
+		}, new ItTraderSteps(classLoader));
+	}
+
+}
+</textarea></p>
+<p>The corresponding I18N-ed <a
+    href=""
+also requires the configuration of I18N-ed keywords: <textarea
+    class="java:nogutter:nocontrols" name="code">
+public class ItTraderSteps extends Steps {
+
+    private Stock stock;
+
+    public ItTraderSteps(ClassLoader classLoader) {
+    	// Use Italian for keywords
+        super(new StepsConfiguration(new I18nKeyWords(new Locale("it"))));
+    }
+
+    @Given("ho un'azione con simbolo $symbol e una soglia di $threshold")
+    public void aStock(@Named("symbol") String symbol, @Named("threshold") double threshold) {
+        stock = new Stock(symbol, threshold);
+    }
+
+    @When("l'azione e' scambiata al prezzo di $price")
+    public void stockIsTraded(@Named("price") double price) {
+        stock.tradeAt(price);
+    }
+
+    @Then("lo status di allerta e' $status")
+    public void alertStatusIs(@Named("status") String status) {
+        ensureThat(stock.getStatus().name(), equalTo(status));
+    }
+
+}
+</textarea></p>
+<p>Note that the I18N-ed keywords not only allow the translation of
+the keywords used in parsing the textual scenario, but also the keywords
+used in the reporting of the scenario execution, e.g. <b>Pending</b>, <b>NotPerformed</b>
+and <b>Failed</b>.</p>
+
+<h2>What if your language is not currently supported?</h2>
+
+<p>You can configure your own bundle, <textarea
+    class="java:nogutter:nocontrols" name="code">
+    
+    String yourBundleName = "path/to/your/keywords"
+    Locale yourLocale = new Locale(...); 
+
+    KeyWords keywords = new KeyWords(yourBundleName, yourLocale);
+</textarea> Just be sure that you use on the existing bundles as a template to
+ensure all the keywords are present.</p>
+<p>Note that by the route you can also override the keywords for a
+locale already supported.</p>
+<p>If you do find yourself providing keywords for a new language, we
+are happy to support it out of the box. Simply get in touch via the <a
+    href="" lists</a> or attach the bundle for
+the new locale to an enhancement request in <a
+    href=""
+
+<div class="clear">
+<hr />
+</div>
+
+</body>
+</html>

Modified: trunk/core/distribution/src/site/content/index.html (1255 => 1256)

--- trunk/core/distribution/src/site/content/index.html	2009-09-19 14:15:10 UTC (rev 1255)
+++ trunk/core/distribution/src/site/content/index.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -1,10 +1,12 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html>
 <head>
-<title>JBehave</title>
+<title>What is JBehave?</title>
 </head>
 
 <body>
+
+<h2>What is JBehave?</h2>
 <p>JBehave is a framework for <a
     href=""
 Development</a> (BDD). BDD is an evolution of test-driven development (TDD)
@@ -13,34 +15,33 @@
 It shifts the vocabulary from being test-based to behaviour-based, and
 positions itself as a design philosophy.</p>
 
-<p>You can find out more about behaviour-driven development on <a
-    href=""
-Newcomers are encouraged to start from <a
-    href="" BDD</a>.</p>
+<p>Features of JBehave include:</p>
 
-<p>Features of JBehave include:
 <ul>
-    <li>Pure Java implementation, which plays well with Java-based enterprises</li>
-    <li>Allows users to specify and run text-based scenarios, which 
+    <li>Pure Java implementation, which plays well with Java-based
+    enterprises</li>
+    <li>Allows users to specify and run text-based scenarios, which
     allows "out-in" development.</li>
     <li>Annotation-based binding of textual steps to Java methods</li>
-    <li>Auto-conversion of string arguments to any
-    parameter type (including generic types) via custom parameter
-    converters.</li>
+    <li>Auto-conversion of string arguments to any parameter type
+    (including generic types) via custom parameter converters.</li>
     <li>Scenario reporter - outputs scenarios executed in
     human-readable form</li>
     <li>Auto-generation of pending steps so the build is not broken
-    by a missing step, but has option to configure breaking build for pending steps.</li>
+    by a missing step, but has option to configure breaking build for
+    pending steps.</li>
     <li>Scenario can be run as JUnit tests, providing easy
-    integration with your favourite IDE.  Using alternative annotation-based
-    unit test frameworks is equally easy.</li>
+    integration with your favourite IDE. Using alternative
+    annotation-based unit test frameworks is equally easy.</li>
     <li>Ant integration: allows scenarios to be run via Ant task</li>
     <li>Maven integration: allows scenarios to be run via Maven
     plugin at given build phase</li>
 </ul>
-</p>
 
-<p>The reference documentation is primarily to provide a reference development guide
-for each release. More dynamic information can be found in <a href="" wiki</a>.</p>
+<h2>Ready for more?</h2>
+<span class="followup">The <a href="" Started</a>
+page will get you up and running in no time.</span>
+
+
 </body>
 </html>
\ No newline at end of file

Added: trunk/core/distribution/src/site/content/parameter-converters.html (0 => 1256)

--- trunk/core/distribution/src/site/content/parameter-converters.html	                        (rev 0)
+++ trunk/core/distribution/src/site/content/parameter-converters.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -0,0 +1,18 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<title>Parameter Converters</title>
+</head>
+
+<body>
+
+<h2>Parameter Converters</h2>
+
+<p>JBehave allows you to define custom parameter converters for user domain types.</p>
+
+<div class="clear">
+<hr />
+</div>
+
+</body>
+</html>
\ No newline at end of file

Added: trunk/core/distribution/src/site/content/parameter-injection.html (0 => 1256)

--- trunk/core/distribution/src/site/content/parameter-injection.html	                        (rev 0)
+++ trunk/core/distribution/src/site/content/parameter-injection.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -0,0 +1,18 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<title>Parameter Injection</title>
+</head>
+
+<body>
+
+<h2>Parameter Injection</h2>
+
+<p>JBehave supports multiple mechanism for parameter injection.</p>
+
+<div class="clear">
+<hr />
+</div>
+
+</body>
+</html>
\ No newline at end of file

Modified: trunk/core/distribution/src/site/content/sitemap.xml (1255 => 1256)

--- trunk/core/distribution/src/site/content/sitemap.xml	2009-09-19 14:15:10 UTC (rev 1255)
+++ trunk/core/distribution/src/site/content/sitemap.xml	2009-09-19 17:48:58 UTC (rev 1256)
@@ -1,7 +1,23 @@
 <sitemap>
+   <section>
+    <name>Reference</name>
+    <page>index.html</page>
+    <page>getting-started.html</page>
+    <page>bdd-concepts.html</page>
+    <page>grammar.html</page>
+    <page>developing-scenarios.html</page>
+    <page>configuring-scenarios.html</page>
+    <page>running-scenarios.html</page>
+    <page>i18n.html</page>        
+    <page>bdd-resources.html</page>
+  </section>
+   <section>
+    <name>Advanced Topics</name>
+    <page>parameter-injection.html</page>
+    <page>parameter-converters.html</page>
+  </section>
   <section>
-    <name>About JBehave</name>
-    <page>index.html</page>
+    <name>Project Information</name>
     <page>license.html</page>
     <page>download.html</page>
     <link title="Issue Tracking">http://jira.codehaus.org/browse/JBEHAVE</link>
@@ -10,12 +26,6 @@
     <page>team-list.html</page>
     <page>source-repository.html</page>
   </section>
-   <section>
-    <name>Using JBehave</name>
-    <page>getting-started.html</page>
-    <page>running-scenarios.html</page>
-    <page>developing-scenarios.html</page>
-  </section>
   <section>
     <name>JavaDoc</name>
     <link title="Core">javadoc/core/index.html</link>

Added: trunk/core/distribution/src/site/resources/scripts/shBrushProperties.js (0 => 1256)

--- trunk/core/distribution/src/site/resources/scripts/shBrushProperties.js	                        (rev 0)
+++ trunk/core/distribution/src/site/resources/scripts/shBrushProperties.js	2009-09-19 17:48:58 UTC (rev 1256)
@@ -0,0 +1,11 @@
+dp.sh.Brushes.Properties = function()
+{
+	this.regexList = [
+		{ regex: dp.sh.RegexLib.SingleLinePerlComments,							css: 'comment' },		// one line comments
+		{ regex: new RegExp('\\b([\\d]+(\\.[\\d]+)?|0x[a-f0-9]+)\\b', 'gi'),	css: 'number' },		// numbers
+	];
+}
+
+dp.sh.Brushes.Properties.prototype	= new dp.sh.Highlighter();
+dp.sh.Brushes.Properties.Aliases	= ['properties'];
+

Modified: trunk/core/distribution/src/site/resources/style/jbehave.css (1255 => 1256)

--- trunk/core/distribution/src/site/resources/style/jbehave.css	2009-09-19 14:15:10 UTC (rev 1255)
+++ trunk/core/distribution/src/site/resources/style/jbehave.css	2009-09-19 17:48:58 UTC (rev 1256)
@@ -82,8 +82,6 @@
   left: 210px;
 }
 
-/* My Comment */
-
 div.section ul li, div.section ol li {
   margin-left: 35px;
 }
@@ -143,6 +141,17 @@
   margin-right: 10px;
 }
 
+.followup {
+  border: 2px solid #39912b;
+  margin: 10px;
+  padding: 4px;
+  color: black;
+  background-color: #99ff99;
+  visibility: visible;
+  overflow: visible;
+  display: table;
+}
+
 /* Menu */
 
 #Menu {

Modified: trunk/core/distribution/src/site/templates/skin.html (1255 => 1256)

--- trunk/core/distribution/src/site/templates/skin.html	2009-09-19 14:15:10 UTC (rev 1255)
+++ trunk/core/distribution/src/site/templates/skin.html	2009-09-19 17:48:58 UTC (rev 1256)
@@ -85,10 +85,11 @@
 <!--  SyntaxHighlighter scripts:  MUST be left AFTER the body -->
 <script language="_javascript_" src=""
 <script language="_javascript_" src=""
+<script language="_javascript_" src=""
+<script language="_javascript_" src=""
 <script language="_javascript_" src=""
+<script language="_javascript_" src=""
 <script language="_javascript_" src=""
-<script language="_javascript_" src=""
-<script language="_javascript_" src=""
 <script type="text/_javascript_">
   dp.SyntaxHighlighter.HighlightAll('code', false, false);
 </script>

To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Reply via email to