cuke4php 0.9.8 → 0.9.9

data/VERSION

@@ -1 +1 @@
-0.9.8
+0.9.9

data/cuke4php.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{cuke4php}
-  s.version = "0.9.8"
+  s.version = "0.9.9"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = [%q{Kevin Olbrich}, %q{Alessandro Dal Grande}]
-  s.date = %q{2011-08-31}
+  s.date = %q{2011-09-05}
   s.description = %q{Using this protocol it is possible to directly interact with PHP code at any level without the need for a web server.  To accomplish this, when cucumber is running against a directory containing feature files and it cannot resolve a particular step definition, it will ask a known wire server (as defined in a .wire file) to interpret and run those steps.}
   s.email = [%q{kevin.olbrich+cuke4php@gmail.com}, %q{aledalgrande@gmail.com}]
   s.executables = [%q{cuke4php_forking_server}, %q{cuke4php_server}, %q{cuke4php}]

data/lib/Cucumber.php

@@ -5,10 +5,12 @@
  */
 
 /**
- * load all php files in this directory
+ * load all php files except the forking server in this directory
+ * Note:  If you require the forking server, it will fail unless pear/Net_Server is installed
  */
-foreach (glob(dirname(__FILE__) . "/*.php") as $sFilename) {
-    require_once $sFilename;
-}
+
+require_once dirname(__FILE__) . "/CucumberScenario.php";
+require_once dirname(__FILE__) . "/CucumberSteps.php";
+require_once dirname(__FILE__) . "/Cuke4php.php";
 
 ?>

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: cuke4php
 version: !ruby/object:Gem::Version 
-  hash: 43
+  hash: 41
   prerelease: 
   segments: 
   - 0
   - 9
-  - 8
-  version: 0.9.8
+  - 9
+  version: 0.9.9
 platform: ruby
 authors: 
 - Kevin Olbrich
@@ -16,7 +16,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-08-31 00:00:00 Z
+date: 2011-09-05 00:00:00 Z
 dependencies: 
 - !ruby/object:Gem::Dependency 
   version_requirements: &id001 !ruby/object:Gem::Requirement