java-helloworld has moved. Remove old Cuke4Duke docs.

Author: aslakhellesoy

CONTRIBUTING.md

@@ -11,7 +11,7 @@ We appreciate that. But before you do, please learn our basic rules:
 
 ## Building Cucumber-JVM
 
-Cucumber-JVM is built with [Maven](http://maven.apache.org/). 
+Cucumber-JVM is built with [Maven](http://maven.apache.org/).
 
 ```
 mvn clean install
@@ -58,7 +58,7 @@ you have changed, and your contribution might get rejected.
 
 ### Running cross-platform Cucumber features
 
-All Cucumber implementations (cucumber-ruby, cucumber-jvm, cucumber-js) share a common set of Cucumber features to 
+All Cucumber implementations (cucumber-ruby, cucumber-jvm, cucumber-js) share a common set of Cucumber features to
 ensure all implementations support the same basic features. To run these you need to clone the cucumber-tck repo into
 your cucumber-jvm working copy:
 
@@ -81,16 +81,6 @@ This can be solved by changing the Compiler settings: `Preferences -> Compiler -
 * *Use compiler:* `Javac`
 * *Additional command line parameters:* `-target 1.6 -source 1.6 -encoding UTF-8`
 
-You should also use JDK 6: `Project Structure... -> Project -> Project SDK`:
-
-* *Use 1.6", not 1.7
-
-If you still have problems, try building the project with Maven, using Java 6:
-
-```
-export JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
-```
-
 Note that even though development is sometimes easier to do with 1.6, releasing should be done with 1.7.
 
 ## Releasing

Cuke4Duke.md

@@ -1,80 +1,3 @@
-## Hello World
-
-This is the simplest possible setup for Cucumber-JVM using Java.
-
-### Ant
-
-Simply run:
-
-```
-ant download
-ant runcukes
-```
-
-This runs Cucumber features using the Command Line Interface (CLI) runner. Note that the `RunCukes` junit class is not used at all.
-If you remove it (and the `cucumber-junit` jar dependency), it will run just the same.
-
-### Maven
-
-Simply run:
-
-```
-mvn test
-```
-
-This runs Cucumber features using the JUnit runner. The `@RunWith(Cucumber.class)` annotation on the `RunCukes` junit class
-kicks off Cucumber.
-
-#### Overriding options
-
-The Cucumber runtime parses command line options to know what features to run, where the glue code lives, what formatters to use etc.
-When you use the JUnit runner, these options are generated from the `@Cucumber.Options` annotation on your test.
-
-Sometimes it can be useful to override these options without changing or recompiling the JUnit class. This can be done with the
-`cucumber.options` system property. The general form is:
-
-Using Maven:
-```
-mvn -Dcucumber.options="..." test
-```
-
-Using Ant:
-```
-JAVA_OPTIONS='-Dcucumber.options="..."' ant runcukes
-```
-
-Let's look at some things you can do with `cucumber.options`. Try this:
-```
--Dcucumber.options="--help"
-```
-
-That should list all the available options.
-
-#### Run a subset of Features or Scenarios
-
-Specify a particular scenario by *line* (and use the pretty format)
-
-```
--Dcucumber.options="classpath:cucumber/examples/java/helloworld/helloworld.feature:4 --format pretty"
-```
-
-This works because Maven puts `./src/test/resources` on your `classpath`.
-You can also specify files to run by filesystem path:
-
-```
--Dcucumber.options="src/test/resources/cucumber/examples/java/helloworld/helloworld.feature:4 --format pretty"
-```
-
-You can also specify what to run by *tag*:
-
-```
--Dcucumber.options="--tags @bar --format pretty"
-```
-
-#### Specify a different formatter:
-
-For example a JUnit formatter:
-```
--Dcucumber.options="--format junit:target/cucumber-junit-report.xml"
-```
+## This example has moved
 
+Please [go here](https://github.com/cucumber/cucumber-java-skeleton).