Sorry I forgot to mention that I updated it already.  I always have my
laptop with me when watching TV and there were nothing interesting on
that day.

On 2/5/07, Dan North <[EMAIL PROTECTED]> wrote:
Great stuff Mauro.

Can you document this on the website please?


Mauro Talevi wrote:
> Hi folks,
>
> the Maven repos have been created at Codehaus.  They are:
>
> - http://repository.codehaus.org/org/jbehave/ - this is for stable and
> versioned releases, which is synched with Maven's Central Repo every
> few hours.
> - http://snapshots.repository.codehaus.org/org/jbehave/ - for snapshots
>
> I've uploaded the latest stable and latest snapshot.
>
> Independently of the synching, you can use the Maven plugin by
> configuring in your POM (typically your parent POM):
>
>    <pluginRepositories>
>         <pluginRepository>
>             <id>codehaus-plugin-repository</id>
>             <name>Codehaus Plugin Repository</name>
>             <url>http://repository.codehaus.org</url>
>         </pluginRepository>
>         <pluginRepository>
>             <id>codehaus-plugin-snapshot-repository</id>
>             <name>Codehaus Plugin Snapshot Repository</name>
>             <url>http://snapshots.repository.codehaus.org</url>
>             <snapshots>
>                 <enabled>true</enabled>
>             </snapshots>
>         </pluginRepository>
>     </pluginRepositories>
>
> If you are just using stable releases, the above configuration becomes
> redundant after a few hours of the release, as the Central Maven Repo
> is configured by default.   These are more useful if you are
> developing and don't want to wait until the synch is done or are using
> snapshot releases.
>
> To use the jBehave plugin in your project
>
>           <plugin>
>                 <groupId>org.jbehave</groupId>
>                 <artifactId>jbehave-maven-plugin</artifactId>
>                 <version>0.9.0</version>
>                 <executions>
>                     <execution>
>                         <phase>integration-test</phase>
>                         <goals>
>                             <goal>run</goal>
>                         </goals>
>                         <configuration>
>                             <behavioursClassName>
>                                 jbehave.AcceptanceBehaviours
>                             </behavioursClassName>
>                         </configuration>
>                     </execution>
>                 </executions>
>             </plugin>
>
> The run goal will verify all the behaviours specified by the
> Behaviours class.
> At the moment, because Behaviours can encode multiple behaviour
> classes, it is a single class that can be specified.  We can easily
> extend it to a list, though.
>
> One thing that I would also like to add is the includes/excludes
> patterns.
>
> Cheers
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>    http://xircles.codehaus.org/manage_email
>


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email




--
Shane
http://www.shaneduan.com

---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to