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 annotated tag, jbehave-3.0-beta-4 has been created
        at  68d86d110d260a0af372aa6b0925c54de2991b59 (tag)
   tagging  4a605b270293430a6f4157f30398355cf3a6f14a (commit)
 tagged by  Mauro Talevi
        on  Tue May 4 01:54:05 2010 +0200

- Log -----------------------------------------------------------------
[maven-release-plugin]  copy for tag jbehave-3.0-beta-4

Mauro Talevi (9):
      Initial import from jbehave 3.0-beta-3
      Merge branch 'jbehave-3.0-beta-3'
      Removed org.jbehave.scenario classes and its usages that had not been 
removed in the merge with jbehave-3.0-beta-3 branch
      JBEHAVE-281:  Ensured the previous step for matching purposes is only a 
non And step, so it can be used to determine the step type compatibility with 
the current step.
      Updated release notes.  Removed obsolete pages remants from 2.x.
      [maven-release-plugin] prepare release jbehave-3.0-beta-4
      Reverted to 3.0-SNAPSHOT version following failed release.
      Fixed repo name in scm connection.
      [maven-release-plugin] prepare release jbehave-3.0-beta-4

mauro (20):
      [maven-release-plugin] prepare for next development iteration
      Updated examples to latest snapshot version.
      JBEHAVE-245:  Only include scenarios classes that are not abstract.
      JBEHAVE-253:  Added SpringApplicationContextFactory.
      JBEHAVE-252:  Improved documentation on scenario and steps configuration.
      JBEHAVE-252:  Improved documentation on scenario and steps configuration.
      [maven-release-plugin] prepare release jbehave-2.5.1
      [maven-release-plugin] prepare for next development iteration
      JBEHAVE-273:  Excluded all core dependencies except paranamer, which is 
shaded
      Removed eclipse files from source control
      JBEHAVE-274:  Added SpringJUnitRunner to trader example
      JBEHAVE-276:  Updated reports configuration and documentation.
      JBEHAVE-277: Allowed specification of output directory in 
ScenarioReporterBuilder as absolute to workaround the issue with Ant's 
classloading that specifies the class code source location as $ANT_HOME/lib.
      Organised imports.
      JBEHAVE-277: Refactored ScenarioReporterBuilder to require explicit 
withDefaultFormats() invocation so it can be done after specification of the 
output directory.
      JBEHAVE-277: Updated reports documentation.
      JBEHAVE-277: Fixed trader example output directory paths.
      JBEHAVE-278:  Enhanced candidate step matching to be aware of the 
previous step type when matching AND steps.
      [maven-release-plugin] prepare release jbehave-2.5.2
      [maven-release-plugin] prepare for next development iteration

paul (3):
      no need to process scenarios that are abstract
      help for folks malconfiguring
      a hybridized resolving strategy

-----------------------------------------------------------------------


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>

Reply via email to