Cucumber step definitions are not being located when running from the command line
<p>Been following along the cucumber book for Java and this example I am working on is very similar to what was in chapter 2. This is on the cmd line as I am not wanting to incorporate in IDE at this point. </p>

<pre><code>Feature: practice test
  Scenario Outline: not CheckingOut bananas
    given abc
    when place holder2
    then place holder3
</code></pre>

<p>The test steps:</p>

<pre><code>public class SimpleTest {
    @Given("^abc")
    public void part1() throws Exception {
        System.out.println("part 1");
        throw new Exception("an exceptoin");
    }

    @When("place holder2")
    public void part2(){
        System.out.println("part 2");
    }

    @Then("place holder3")
    public void part3() {
        System.out.println("part 3");
    }

}
</code></pre>

<p>I've tried the "abc", "^abc", "give abc"... on the @Given</p>

<p>I am driving this with the following bat file and the step definitions do compile and the class file is there. I realize on the -g (glue) option that the package name is the argument value so I made this as simple as possible 
but I am getting 0 scenarios found. The bat file is simple:</p>

<pre><code>echo cucumber compile and execution
javac -cp "lib/*" step_definitions/SimpleTest.java 
javac -cp "lib/*;web/WEB-INF/lib/*" test/java/xxxxx/zzzz/referral/out/batch/RunCukesTest.java 
java -cp "lib/*;web/WEB-INF/lib/*;.;test/java/*" cucumber.api.cli.Main -p pretty -g step_definitions features
</code></pre>

<p>consistently I get the following results:</p>

<pre><code>Feature: practice test

  Scenario Outline: not CheckingOut bananas ←[90m# bogus.feature:2←[0m
    given abc
    when place holder2
    then place holder3


0 Scenarios
0 Steps
0m0.000s
</code></pre>

<p>Clearly the CLI is finding the feature file but the compiled step definitions are not being found. Doubt it is a class path issue. I've provided extra dirs and have moved the step definition file around. the CLI is not taking the feature file and matching it to the compiled definitions. Thanks ahead of time. A lot of times typing out these questions the solution is realized but on this it is not. </p>

<p>If the *.feature files are a requirement for cucumber to run and that they must correspond to a compiled step definition even if junit is hooks into the cucumber.class test runnner, the book could have left less room uncertainty. 
The forum for the book looked thin. Probably need to go to github or wherever the source code is. </p>