Remove duplicated lines

Nice work! @jtigger

- ensure titles of tests match those in
  https://github.com/exercism/x-common/blob/master/exercises/pangram/canonical-data.json

Update ABOUT.md

Add quick start guide

Ignore all but first test in hello-world

- in journey test, remove @Ignores so that test runs exercise all tests.
- increase the verbosity of test logging to aide in seeing progress as
  tests are un@Ignored and solved.
- saving scripts used to make changes to all exercises.  These are the
  start of a library of scripts making such changes easier.
- make Gradle output more CI-friendly.

- in base build script, filter out @Ignores so that maintainers can run
  the full test suites.
- increase the verbosity of test logging to aide in seeing progress as
  tests are un@Ignored and solved.
- revamped GETTING_STARTED.md to reflect new output.  It is now a
  complete guide from start to finish with calls-to-action at the end of
  the instructions.

Initial POC of how to ignore all-but-first test

Describe how to get started with an exercise.

- Ensure only installation instructions are in INSTALLATION.md and only
  instructions for running tests are in TESTS.md.
- Remove install instructions for IDEs:
  - IDEs start to pay dividends when your codebase gets large enough that the refactoring and code navigation features start to seriously increase your efficiency; Exercism programs are, by design, toy-sized;
  - There are far fewer instructions to getting started when doing it from the command-line (and therefore less likely to get wrong).
- Focus on using package managers:
  - these tools provide the right kind of "magic" — you really don't need to know the installation details to start programming;
  - they automatically perform steps that can be hard to describe and do right (less likely to get wrong).

Add track icon.

Describe "simple" setup, leveraging the CI build.

Add there "exercises" key to config.json

- trimmed a bunch: the fewer words used, the more words read.
- removed step-by-step full setup in favor of referring to the CI
  script.

First step in transitioning from "problems" to "exercises".

Part of exercism/xjava#125.

Fixed typo "but the tests are expects"

A (partial) fix for the issue #2670

Use same version of Ruby X-API is: now 2.2.5.

dibs: I will implement exercise beer-song

Merge journey test scripts into one.

CI runs journey test

- otherwise this journey is testing not the latest copy of xjava, but
  what's at origin/master.
- add progress indicator.
- x-api can't serve binaries; must clean xjava of any build artifacts
  (e.g. .class files) before attempting to serve.

Signed-off-by: Bronwyn Perry-Huston <bronhuston@gmail.com>
Signed-off-by: Cen Ge <cge@corelogic.com>
Signed-off-by: John Ryan <jtigger@infosysengr.com>

Signed-off-by: Cen Ge <cge@corelogic.com>
Signed-off-by: Dan Neumann <dan@bestangle.com>
Signed-off-by: John Ryan <jtigger@infosysengr.com>

- golang 1.4 networking libs favor IPv4; x-api listening on IPv6
  localhost.
- need golang 1.5+

Signed-off-by: Bronwyn Perry-Huston <bronhuston@gmail.com>
Signed-off-by: Cen Ge <cge@corelogic.com>
Signed-off-by: John Ryan <jtigger@infosysengr.com>

Signed-off-by: Cen Ge <cge@corelogic.com>
Signed-off-by: Dan Neumann <dan@bestangle.com>
Signed-off-by: John Ryan <jtigger@infosysengr.com>

- clone x-api
- use proper version of ruby.

Signed-off-by: Bronwyn Perry-Huston <bronhuston@gmail.com>
Signed-off-by: Cen Ge <cge@corelogic.com>
Signed-off-by: John Ryan <jtigger@infosysengr.com>

Add canonical cases to test

Fix typo in test name

As I don't think the month of Map exists, I'm guessing this is meant to be May :)

Modify README to clarify instructions

Uppercase oxyphenbutazone

Introduce a new JUnit test category that lets us mark certain tests as
not ready for execution. The test task in the individual project
can then be configured to not run tests marked as `NotReady`.

For the CI server builds, add a fullTest test task that simply runs
tests as normal, and link it into the check task so it runs on builds.

This is not perfect, as the class under test must still compile, so it
must have at least the correct signatures of all the methods tested.
Also, it may be worth finding a way to distribute the NotReady interface
that doesn't require checking it into every project.