trackler 2.1.0.41 → 2.1.0.42

data/tracks/fsharp/config.json

@@ -1,7 +1,7 @@
 {
   "slug": "fsharp",
   "language": "F#",
-  "repository": "https://github.com/exercism/xfsharp",
+  "repository": "https://github.com/exercism/fsharp",
   "active": true,
   "exercises": [
     {

data/tracks/go/README.md

@@ -1,33 +1,33 @@
-# xGo
+# Exercism Go Track
 
-[![Build Status](https://travis-ci.org/exercism/xgo.png?branch=master)](https://travis-ci.org/exercism/xgo)
+[![Build Status](https://travis-ci.org/exercism/go.png?branch=master)](https://travis-ci.org/exercism/go)
 
 Exercism exercises in Go
 
 ## Issues
 
-We welcome issues filed at https://github.com/exercism/xgo/issues for problems of any size.  Feel free to report
+We welcome issues filed at https://github.com/exercism/go/issues for problems of any size.  Feel free to report
 typographical errors or poor wording.  We are most interested in improving the quality of the test suites.
 You can greatly help us improve the quality of the exercises by filing reports of invalid solutions that
 pass tests or of valid solutions that fail tests.
 
 ## Development setup
 
-Beyond filing issues, if you would like to contribute directly to the Go code in xgo, you should follow some
+Beyond filing issues, if you would like to contribute directly to the Go code in the Exercism Go track, you should follow some
 standard Go development practices.  You should have a [recent version of Go](http://golang.org/doc/install)
 installed, ideally either the current release, the previous release, or tip.
 
-You will need a github account and you will need to fork exercism/xgo to your account.
+You will need a github account and you will need to fork exercism/go to your account.
 See [GitHub Help](https://help.github.com/articles/fork-a-repo/) if you are unfamiliar with the process.
-Clone your fork with the command: `git clone https://github.com/<you>/xgo`.
-Test your clone by cding to the xgo directory and typing
+Clone your fork with the command: `git clone https://github.com/<you>/go`.
+Test your clone by cding to the go directory and typing
 `bin/test-without-stubs`. You should see tests pass for all exercises.
 
 Note that unlike most other Go code, it is not necessary to clone this to your GOPATH.
 This is because this repo only imports from the standard library and isn't expected to be imported by other packages.
 
 There is a [misspelling tool](https://github.com/client9/misspell). You can install and occasionally run it to
-find low hanging typo problems. [#570](https://github.com/exercism/xgo/pull/570) It's not added into CI since it could give false positives.
+find low hanging typo problems. [#570](https://github.com/exercism/go/pull/570) It's not added into CI since it could give false positives.
 
 ## Contributing Guide
 
@@ -35,7 +35,7 @@ Please be familiar with the [contributing guide](https://github.com/exercism/doc
 in the docs repository.  This describes some great ways to get involved.
 In particular, please read the [Pull Request Guidelines](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks/pull-request-guidelines.md) before opening a pull request.
 
-## xgo style
+## Exercism Go style
 
 Let's walk through the `leap` exercise to see what is included in an exercise
 implementation. Navigate into the *leap* directory, you'll see there are a
@@ -96,7 +96,7 @@ an exercise is fetched. These are:
 
 ### Example solutions
 
-*example.go* is a reference solution. It is a valid solution that [Travis](https://travis-ci.org/exercism/xgo),
+*example.go* is a reference solution. It is a valid solution that [Travis](https://travis-ci.org/exercism/go),
 the CI (continuous integration) service, can run tests against. Solvers generally
 will not see it though. Files with *"example"* in the file name are skipped by
 the `exercism fetch` command. Because of this, there is less need for this code
@@ -142,7 +142,7 @@ that document the exercise API. These examples are run alongside the standard
 exercise tests and will verify that the exercise API is working as expected.
 They are not required by all exercises and are not intended to replace the
 data-driven tests. They are most useful for providing examples of how an
-exercise's API is used. Have a look at the example tests in the [clock exercise](https://github.com/exercism/xgo/blob/master/exercises/clock/example_clock_test.go)
+exercise's API is used. Have a look at the example tests in the [clock exercise](https://github.com/exercism/go/blob/master/exercises/clock/example_clock_test.go)
 to see them in action.
 
 ### Stub files
@@ -164,7 +164,7 @@ difficult concept, or boilerplate code needed.
 ### Problem Versioning
 
 Each problem defines a `const targetTestVersion` in the test file, and validates
-that the solution has defined a matching value `testVersion`. Any xgo developer
+that the solution has defined a matching value `testVersion`. Any Go track developer
 that changes the test file or test data must increment `targetTestVersion`.
 
 The benefit of all this is that reviewers can see which test version a posted
@@ -202,16 +202,16 @@ If there isn't one it will attempt to get the relevant json data for the
 exercise from the **x-common** repository on GitHub.
 
 To use a local copy of the **x-common** repository, make sure that it has been
-cloned into the same parent-directory as the **xgo** repository.
+cloned into the same parent-directory as the **go** repository.
 
 ```sh
 $ tree -L 1 .
 .
 ├── x-common
-└── xgo
+└── go
 ```
 
-To regenerate the test cases, navigate into the **xgo** directory and run
+To regenerate the test cases, navigate into the **go** directory and run
 `go run exercises/<exercise>/.meta/gen.go`. You should see that the
 `<exercise>/cases_test.go` file has changed. Commit the change.
 
@@ -224,7 +224,7 @@ and the invitation to submit a pull request!
 <img src="img/mars1.png">
 
 Click on that big green button.  You have a chance to add more explanation to your pull request here, then send
-it.  Looking at the exercism/xgo repository now instead of your own, you see this.
+it.  Looking at the exercism/go repository now instead of your own, you see this.
 
 <img src="img/mars2.png">
 

data/tracks/go/config.json

@@ -1,7 +1,7 @@
 {
   "slug": "go",
   "language": "Go",
-  "repository": "https://github.com/exercism/xgo",
+  "repository": "https://github.com/exercism/go",
   "active": true,
   "ignore_pattern": "example(?!.*test)",
   "deprecated": [

data/tracks/go/exercises/gigasecond/gigasecond_test.go

@@ -52,8 +52,8 @@ func parse(s string, t *testing.T) time.Time {
 			t.Fatal(err)
 		} else {
 			t.Log(err)
-			t.Skip("(Not your problem.  " +
-				"please file issue at https://github.com/exercism/xgo.)")
+			t.Skip("(This is not your fault, and is unexpected.  " +
+				"Please file an issue at https://github.com/exercism/go.)")
 		}
 	}
 	return tt

data/tracks/go/gen/gen.go

@@ -19,13 +19,13 @@ import (
 
 // dirMetadata is the location of the x-common repository on the filesystem.
 // We're making the assumption that the x-common repository has been cloned to
-// the same parent directory as the xgo repository.
+// the same parent directory as the Exercism Go track repository.
 // E.g.
 //
 //     $ tree -L 1 .
 //     .
 //     ├── x-common
-//     └── xgo
+//     └── go
 var dirMetadata string
 
 // dirExercise is the location that the test cases should be generated to.

data/tracks/haskell/.gitignore

@@ -2,7 +2,7 @@
 bin/configlet
 bin/configlet.exe
 
-# exercism/xhaskell specific patterns
+# exercism/haskell specific patterns
 *.cabal
 
 # sorted default .gitignore from github/gitignore/Haskell.gitignore

data/tracks/haskell/README.md

@@ -1,6 +1,6 @@
-# xHaskell
+# Exercism Haskell Track
 
-[![Build Status](https://travis-ci.org/exercism/xhaskell.png?branch=master)](https://travis-ci.org/exercism/xhaskell)
+[![Build Status](https://travis-ci.org/exercism/haskell.png?branch=master)](https://travis-ci.org/exercism/haskell)
 
 Exercism exercises in Haskell
 
@@ -43,19 +43,22 @@ problem description.
 - If you already have a fix for it you may [write a pull request](#writing-a-pull-request).
 
 #### Reviewing issues and pull requests
-If you have a dedicated opinion you are welcome to [write a comment](https://help.github.com/articles/commenting-on-a-pull-request/) for an [issue](https://github.com/exercism/xhaskell/issues) or a [pull request](https://github.com/exercism/xhaskell/pulls).
+If you have a dedicated opinion you are welcome to [write a comment](https://help.github.com/articles/commenting-on-a-pull-request/) for an [issue](https://github.com/exercism/haskell/issues) or a [pull request](https://github.com/exercism/haskell/pulls).
 Please be detailed and include reasons, links or arguments to support your opinion.
 
 #### Porting exercises
-Here is the [list of missing exercises](http://exercism.io/languages/haskell/todo). See here for more information about [porting an exercise](https://github.com/exercism/x-common/blob/master/CONTRIBUTING.md#porting-an-exercise-to-another-language-track).
+The site contains a [list of missing exercises](http://exercism.io/languages/haskell/todo).
+You may implement any of these exercises for the Haskell track.
+Feel free to refer to the [documentation on porting an exercise](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks/porting-an-exercise.md).
 Of course you can also add a totally new exercise, but it might be a good idea to first discuss it in one of [our forums](#asking-for-help).
 
 #### Updating an exercise test suite
-Updating a test suite of an existing exercise is special because it usually affects all languages. Read more about it [here](https://github.com/exercism/x-common/blob/master/CONTRIBUTING.md#updating-an-exercise-test-suite).
+Updating a test suite of an existing exercise is special because it usually affects all languages.
+You can refer to the [documentation on updating a test suite](https://github.com/exercism/x-common/blob/master/CONTRIBUTING.md#updating-an-exercise-test-suite).
 Note that the whole test suite must run with the sample solution within a couple of seconds.
 
 ### Repository structure and conventions
-[Here](https://github.com/exercism/x-common/blob/master/CONTRIBUTING.md#track-anatomy) is a general description of all the files and directories that are not explicitly described below.
+The [track anatomy documentation](https://github.com/exercism/x-common/blob/master/CONTRIBUTING.md#track-anatomy) is a general description of all the files and directories that are not explicitly described below.
 
 #### Directory structure
 ```bash
@@ -107,10 +110,11 @@ format that has all dependencies and build instructions for an exercise.
 - `test/Tests.hs` is the [test suite](#test-suite).
 
 ### Writing an issue
-To report a bug you should [create an issue](https://help.github.com/articles/creating-an-issue/) [here](https://github.com/exercism/xhaskell/issues).
+To report a bug you should [create an issue](https://help.github.com/articles/creating-an-issue/) on the [exercism/haskell repo](https://github.com/exercism/haskell/issues).
 
 ### Writing a pull request
-To fix a bug you should [create a pull request from a fork](https://help.github.com/articles/creating-a-pull-request-from-a-fork/) [here](https://github.com/exercism/xhaskell/pulls). See also [here](https://github.com/exercism/x-common/blob/master/CONTRIBUTING.md#git-basics) for more information.
+To fix a bug you should [create a pull request from a fork](https://help.github.com/articles/creating-a-pull-request-from-a-fork/) on the [exercism/haskell repo](https://github.com/exercism/haskell/pulls).
+If you need help with Git, we have some [documentation on Git basics](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks/git-basics.md).
 
 ### Development Dependencies
 You should have [Stack](http://docs.haskellstack.org/) installed in your system to make contributing to this repository easier.

data/tracks/haskell/config.json

@@ -1,7 +1,7 @@
 {
   "slug": "haskell",
   "language": "Haskell",
-  "repository": "https://github.com/exercism/xhaskell",
+  "repository": "https://github.com/exercism/haskell",
   "active": true,
   "exercises": [
     {

data/tracks/haskell/docs/EXERCISE_README_INSERT.md

@@ -45,7 +45,7 @@ stack ghci
 
 ## Feedback, Issues, Pull Requests
 
-The [exercism/xhaskell](https://github.com/exercism/xhaskell) repository on
+The [exercism/haskell](https://github.com/exercism/haskell) repository on
 GitHub is the home for all of the Haskell exercises.
 
 If you have feedback about an exercise, or want to help implementing a new

data/tracks/idris/README.md

@@ -1,4 +1,4 @@
-# xIdris
+# Exercism Idris Track
 
 Exercism problems in Idris.
 

data/tracks/idris/config.json

@@ -1,7 +1,7 @@
 {
   "slug": "idris",
   "language": "Idris",
-  "repository": "https://github.com/exercism/xidris",
+  "repository": "https://github.com/exercism/idris",
   "active": false,
   "deprecated": [
 

data/tracks/java/POLICIES.md

@@ -30,7 +30,7 @@ Our policies are not set-in-stone. They represent directions chosen at a point i
 
 > Most (all?) exercises should be implemented in the form of instance methods since they contain "domain logic" and we (Exercism) want to encourage exemplary software.
 
-References: [[1](https://github.com/exercism/xjava/issues/177#issuecomment-261291741)]
+References: [[1](https://github.com/exercism/java/issues/177#issuecomment-261291741)]
 
 ### Starter implementations
 
@@ -40,7 +40,7 @@ References: [[1](https://github.com/exercism/xjava/issues/177#issuecomment-26129
     `throw new UnsupportedOperationException("Delete this statement and provide your own implementation.");`
 > - Exercises 21+: provide no stubs, but mention any "interesting" interface aspects in the HINT.md file (which gets merged into the README.md for the exercise).
 
-References: [[1](https://github.com/exercism/xjava/issues/178)]
+References: [[1](https://github.com/exercism/java/issues/178)]
 
 ### Do not make user-facing classes `final`
 
@@ -50,22 +50,22 @@ References: [[1](https://github.com/exercism/xjava/issues/178)]
 
 > All but the first test in an exercise test suite should be annotated `@Ignore("Remove to run test")` (single test) or `@Ignore("Remove to run tests")` (parametrized test).
 
-References: [[1](https://github.com/exercism/xjava/issues/101#issuecomment-249349204)]
+References: [[1](https://github.com/exercism/java/issues/101#issuecomment-249349204)]
 
 ### Multiple file submissions
 
 > The first exercise in the track whose test suite mandates multiple solution files should be accompanied by a HINT.md file reminding the practitioner that the CLI supports multiple file submissions.
 
-References: [[1](https://github.com/exercism/xjava/issues/365#issuecomment-292533120)]
+References: [[1](https://github.com/exercism/java/issues/365#issuecomment-292533120)]
 
 ### Good first patches
 
-> Aim to keep 10-20 small and straightforward issues open at eny given time. Identify any such issues by applying the "Good first patch" label. You can view the current list of these issues [here](https://github.com/exercism/xjava/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+patch%22).
+> Aim to keep 10-20 small and straightforward issues open at eny given time. Identify any such issues by applying the "Good first patch" label. You can view the current list of these issues [here](https://github.com/exercism/java/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+patch%22).
 
-References: [[1](https://github.com/exercism/xjava/issues/220#issue-196447088)]
+References: [[1](https://github.com/exercism/java/issues/220#issue-196447088)]
 
 ### Simple onboarding
 
 > The Installing Java instructions should seek to minimize the number of steps and the number of concepts a new-to-the-track practitioner needs to learn to get to coding.
 
-References: [[1](https://github.com/exercism/xjava/issues/395#issue-215734887)]
+References: [[1](https://github.com/exercism/java/issues/395#issue-215734887)]

data/tracks/java/README.md

@@ -1,4 +1,4 @@
-# xJava [![Build Status](https://travis-ci.org/exercism/xjava.svg?branch=master)](https://travis-ci.org/exercism/xjava) [![Join the chat at https://gitter.im/exercism/xjava](https://badges.gitter.im/exercism/xjava.svg)](https://gitter.im/exercism/xjava?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+# java [![Build Status](https://travis-ci.org/exercism/java.svg?branch=master)](https://travis-ci.org/exercism/java) [![Join the chat at https://gitter.im/exercism/xjava](https://badges.gitter.im/exercism/java.svg)](https://gitter.im/exercism/xjava?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
 Source for Exercism Exercises in Java.
 
@@ -32,13 +32,13 @@ To submit a fix for an existing exercise or port an exercise to Java with the le
 1. **Ensure you have the basic Java tooling installed:**  JDK 1.8+, an editor and Gradle 2.x.
 
    (see [exercism.io: Installing Java](http://exercism.io/languages/java/installing))
--  **Setup a branch on a fork of [exercism/xjava](https://github.com/exercism/xjava) on your computer.**
+-  **Setup a branch on a fork of [exercism/java](https://github.com/exercism/java) on your computer.**
 
    See [GitHub Help: Forking](https://help.github.com/articles/fork-a-repo/).  Use those instructions (in conjunction with [Exercism Contributing Guide](https://github.com/exercism/x-common/blob/master/CONTRIBUTING.md#git-basics)) to:
    * "fork" a repository on GitHub;
    - install `git`;
    - "clone" a copy of your fork;
-   - configure an "upstream remote" (in this case, `exercism/xjava`);
+   - configure an "upstream remote" (in this case, `exercism/java`);
    - create a branch to house your work
 -  **Write the codes.**  Do your work on that branch you just created.
 
@@ -59,8 +59,8 @@ To submit a fix for an existing exercise or port an exercise to Java with the le
 
 There are two objectives to the design of this build:
 
-1. when a problem is built from within the xjava repo, the tests run against the "example" code (i.e. when you, the contributor, are developing the exercise);
-2. when a problem is built outside the xjava repo (when a participant is solving the exercise), the tests run against the "main" code.
+1. when a problem is built from within the `exercism/java` repo, the tests run against the "example" code (i.e. when you, the contributor, are developing the exercise);
+2. when a problem is built outside the `exercism/java` repo (when a participant is solving the exercise), the tests run against the "main" code.
 
 This repo is a multi-project gradle build.
 
@@ -109,10 +109,10 @@ and if you review the logs of your x-api, you'll find:
 2015-09-06 15:21:01 - JSON::GeneratorError - source sequence is illegal/malformed utf-8:
 ```
 
-This is because some files generated by the build can't be served from the x-api.  This is by design: the CLI does not serve binaries.  To fix this, simply make sure you do a clean in your `xjava` repo before you fetch:
+This is because some files generated by the build can't be served from the x-api.  This is by design: the CLI does not serve binaries.  To fix this, simply make sure you do a clean in your `exercism/java` repo before you fetch:
 
 ```
-cd ~/workspace/exercism/xjava/exercises
+cd ~/workspace/exercism/java/exercises
 gradle clean
 cd ~/workspace/exercism/exercises
 exercism fetch java bob

data/tracks/java/bin/journey-test.sh

@@ -3,7 +3,7 @@
 # This script is shared between the Java and Kotlin tracks.  If you make an update to this script on
 # one track, please create a companion PR to merge it in to the other.  Thank you!
 TRACK=java
-TRACK_REPO="x${TRACK}"
+TRACK_REPO="$TRACK"
 TRACK_SRC_EXT="java"
 
 on_exit() {

data/tracks/java/config.json

@@ -1,7 +1,7 @@
 {
   "slug": "java",
   "language": "Java",
-  "repository": "https://github.com/exercism/xjava",
+  "repository": "https://github.com/exercism/java",
   "active": true,
   "exercises": [
     {

data/tracks/java/docs/MAINTAINING.md

@@ -4,23 +4,22 @@ This is a guide/reference for maintainers of the Java track.
 
 - [Your Permissions](#your-permissions)
 - [Maintainer Guides](#maintainer-guides)
-- [The Project Board](#the-project-board)
 - [Miscellaneous](#miscellaneous)
 
 ## Your Permissions 
 
-As a maintainer, you have write access to four repositories.  "write access" means you can: review, reject, accept and merge PRs; and push changes to these repos.  Despite having permissions to push directly, we tend to seek review of even our own PRs.
+As a maintainer, you have write access to several repositories.  "write access" means you can: review, reject, accept and merge PRs; and push changes to these repos.  Despite having permissions to push directly, we tend to seek review of even our own PRs.
 
 ### Track-specific
 
-- [xjava](https://github.com/exercism/xjava) — yeah... you know what this one is. :)
+- [java](https://github.com/exercism/java) — yeah... you know what this one is. :)
 
 ### Exercism-wide
 
 - [x-common](https://github.com/exercism/x-common) — the library of canonical exercises.
 - [discussions](https://github.com/exercism/discussions) — the place where project-wide conversations happen. 
   [issues sorted by most recently updated.](https://github.com/exercism/discussions/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)
-- [todo](https://github.com/exercism/todo) — not really used... might just go away completely in the future.
+- [docs](https://github.com/exercism/docs) - the place to find project-wide documentation.
 
 ## Maintainer Guides
 
@@ -28,22 +27,6 @@ As a maintainer, you have write access to four repositories.  "write access" mea
 - [exercism.io/docs/getting-involved-in-a-track.md](https://github.com/exercism/exercism.io/blob/master/docs/getting-involved-in-a-track.md)
 - [exercism.io/docs/reviewing-a-pull-request.md](https://github.com/exercism/exercism.io/blob/master/docs/reviewing-a-pull-request.md)
 
-## The Project Board
-
-GitHub issues are great, but there's no way to easily set priorities.
-To do this, we're using a GitHub Project: https://github.com/exercism/xjava/projects/2.
-
-- **Epics** — issues that really represent bigger ideas.  These inspire creating a set of smaller issues to be elaborated...
-- **Icebox** — issues that just needs a little more detail to be "ready to play"...
-- **Backlog** — issues ready to be worked.  When we start working on an issue, we move it to the next column...
-- **Current** — issues in progress.  When we've considered it done, we move the card to...
-- **Delivered** — completed issues that could use another pair of eyes.  When these are reviewed they get moved to...
-- **Done** — issues we've complete.  Every so often, we get together and it's nice to review what we've completed. 
-  Once reviewed, we remove them from this Project.
-
-The point of this board is to make clear our shared priorities.  It's a tool you can use.
-However, if you have an idea and want to implement it, you can just do it; it does not have to be added to this board.
-
 ## Miscellaneous
 
 - Issues marked with "policy" are current "team agreements": [exercism?label:policy](https://github.com/search?q=org%3Aexercism+label%3Apolicy).

data/tracks/java/docs/TESTS.md

@@ -37,7 +37,7 @@ Choose your operating system:
    C:\Users\JohnDoe>gradle test
    ```
    *(Don't worry about the tests failing, at first, this is how you begin each exercise.)*
-5. Solve the exercise.  Find and work through the `GETTING_STARTED.md` guide ([view on GitHub](https://github.com/exercism/xjava/blob/master/exercises/hello-world/GETTING_STARTED.md)).
+5. Solve the exercise.  Find and work through the `GETTING_STARTED.md` guide ([view on GitHub](https://github.com/exercism/java/blob/master/exercises/hello-world/GETTING_STARTED.md)).
 
 
 Good luck!  Have fun!
@@ -70,7 +70,7 @@ If you get stuck, at any point, don't forget to reach out for [help](http://exer
   $ gradle test
   ```
    *(Don't worry about the tests failing, at first, this is how you begin each exercise.)*
-4. Solve the exercise.  Find and work through the `GETTING_STARTED.md` guide ([view on GitHub](https://github.com/exercism/xjava/blob/master/exercises/hello-world/GETTING_STARTED.md)).
+4. Solve the exercise.  Find and work through the `GETTING_STARTED.md` guide ([view on GitHub](https://github.com/exercism/java/blob/master/exercises/hello-world/GETTING_STARTED.md)).
 
 Good luck!  Have fun!
 
@@ -102,7 +102,7 @@ If you get stuck, at any point, don't forget to reach out for [help](http://exer
   $ gradle test
   ```
    *(Don't worry about the tests failing, at first, this is how you begin each exercise.)*
-4. Solve the exercise.  Find and work through the `GETTING_STARTED.md` guide ([view on GitHub](https://github.com/exercism/xjava/blob/master/exercises/hello-world/GETTING_STARTED.md)).
+4. Solve the exercise.  Find and work through the `GETTING_STARTED.md` guide ([view on GitHub](https://github.com/exercism/java/blob/master/exercises/hello-world/GETTING_STARTED.md)).
 
 Good luck!  Have fun!
 

data/tracks/java/exercises/all-your-base/src/test/java/BaseConverterTest.java

@@ -7,6 +7,9 @@ import java.util.Arrays;
 
 import static org.junit.Assert.assertArrayEquals;
 
+/*
+ * version: 1.1.0
+ */
 public class BaseConverterTest {
 
     /*
@@ -197,69 +200,69 @@ public class BaseConverterTest {
 
     @Ignore("Remove to run test")
     @Test
-    public void testNegativeDigit() {
+    public void testFirstBaseIsOne() {
         expectedException.expect(IllegalArgumentException.class);
-        expectedException.expectMessage("Digits may not be negative.");
+        expectedException.expectMessage("Bases must be at least 2.");
 
-        new BaseConverter(2, new int[]{1, -1, 1, 0, 1, 0});
+        new BaseConverter(1, new int[]{});
     }
 
     @Ignore("Remove to run test")
     @Test
-    public void testInvalidPositiveDigit() {
+    public void testFirstBaseIsZero() {
         expectedException.expect(IllegalArgumentException.class);
-        expectedException.expectMessage("All digits must be strictly less than the base.");
+        expectedException.expectMessage("Bases must be at least 2.");
 
-        new BaseConverter(2, new int[]{1, 2, 1, 0, 1, 0});
+        new BaseConverter(0, new int[]{});
     }
 
     @Ignore("Remove to run test")
     @Test
-    public void testFirstBaseIsOne() {
+    public void testFirstBaseIsNegative() {
         expectedException.expect(IllegalArgumentException.class);
         expectedException.expectMessage("Bases must be at least 2.");
 
-        new BaseConverter(1, new int[]{});
+        new BaseConverter(-2, new int[]{});
     }
 
     @Ignore("Remove to run test")
     @Test
-    public void testSecondBaseIsOne() {
-        final BaseConverter baseConverter = new BaseConverter(2, new int[]{1, 0, 1, 0, 1, 0});
-
+    public void testNegativeDigit() {
         expectedException.expect(IllegalArgumentException.class);
-        expectedException.expectMessage("Bases must be at least 2.");
+        expectedException.expectMessage("Digits may not be negative.");
 
-        baseConverter.convertToBase(1);
+        new BaseConverter(2, new int[]{1, -1, 1, 0, 1, 0});
     }
 
     @Ignore("Remove to run test")
     @Test
-    public void testFirstBaseIsZero() {
+    public void testInvalidPositiveDigit() {
         expectedException.expect(IllegalArgumentException.class);
-        expectedException.expectMessage("Bases must be at least 2.");
+        expectedException.expectMessage("All digits must be strictly less than the base.");
 
-        new BaseConverter(0, new int[]{});
+        new BaseConverter(2, new int[]{1, 2, 1, 0, 1, 0});
     }
 
     @Ignore("Remove to run test")
     @Test
-    public void testSecondBaseIsZero() {
+    public void testSecondBaseIsOne() {
         final BaseConverter baseConverter = new BaseConverter(2, new int[]{1, 0, 1, 0, 1, 0});
 
         expectedException.expect(IllegalArgumentException.class);
         expectedException.expectMessage("Bases must be at least 2.");
 
-        baseConverter.convertToBase(0);
+        baseConverter.convertToBase(1);
     }
 
     @Ignore("Remove to run test")
     @Test
-    public void testFirstBaseIsNegative() {
+    public void testSecondBaseIsZero() {
+        final BaseConverter baseConverter = new BaseConverter(2, new int[]{1, 0, 1, 0, 1, 0});
+
         expectedException.expect(IllegalArgumentException.class);
         expectedException.expectMessage("Bases must be at least 2.");
 
-        new BaseConverter(-2, new int[]{});
+        baseConverter.convertToBase(0);
     }
 
     @Ignore("Remove to run test")

data/tracks/java/exercises/hello-world/GETTING_STARTED.md

@@ -5,7 +5,7 @@ This guide picks-up where [Running the Tests (in Java)](http://exercism.io/langu
 left off.  If you haven't reviewed those instructions, do so now.
 
 Need more information?  A **step-by-step tutorial** is available in this directory at TUTORIAL.md or you can read 
-the [HTML version](https://github.com/exercism/xjava/blob/master/exercises/hello-world/TUTORIAL.md).
+the [HTML version](https://github.com/exercism/java/blob/master/exercises/hello-world/TUTORIAL.md).
 
 The following instructions work equally well on Windows, Mac OS X and Linux.
 

data/tracks/java/exercises/hello-world/TUTORIAL.md

@@ -1,5 +1,5 @@
 NOTE: You can also view the HTML version of this file here:
-https://github.com/exercism/xjava/blob/master/exercises/hello-world/TUTORIAL.md
+https://github.com/exercism/java/blob/master/exercises/hello-world/TUTORIAL.md
 
 * [Solving "Hello, World!"](#solving-hello-world)
  * [Reading Gradle output](#reading-gradle-output)
@@ -93,7 +93,7 @@ FAILURE: Build failed with an exception.
 
 * What went wrong:
 Execution failed for task ':test'.
-> There were failing tests. See the report at: file:///Users/jtigger/projects/exercism/xjava/build/exercism/java/hello-world/build/reports/tests/index.html
+> There were failing tests. See the report at: file:///Users/jtigger/projects/exercism/java/build/exercism/java/hello-world/build/reports/tests/index.html
 
 * Try:
 Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

data/tracks/javascript/config.json

@@ -1,7 +1,7 @@
 {
   "slug": "javascript",
   "language": "JavaScript",
-  "repository": "https://github.com/exercism/xjavascript",
+  "repository": "https://github.com/exercism/javascript",
   "active": true,
   "test_pattern": ".*[.]spec[.]js$",
   "exercises": [

data/tracks/julia/.travis.yml

@@ -6,12 +6,10 @@ os:
 julia:
   - nightly
   - 0.6
-  - 0.5
 
 matrix:
   allow_failures:
     - julia: nightly
-    - julia: 0.6
 
 script:
   - julia runtests.jl

data/tracks/julia/config.json

@@ -215,6 +215,15 @@
         "mathematics"
       ]
     },
+    {
+      "slug": "robot-name",
+      "difficulty": 2,
+      "topics": [
+        "structs",
+        "strings",
+        "randomness"
+      ]
+    },
     {
       "slug": "rotational-cipher",
       "difficulty": 2,

data/tracks/julia/exercises/custom-set/example.jl

@@ -1,7 +1,7 @@
 import Base: AbstractSet, isempty, length, in, issubset, start, next, done,
              push!, ==, copy, intersect!, intersect, union!, union
 
-type CustomSet{T} <: AbstractSet
+struct CustomSet{T} <: AbstractSet{T}
     elements::Array{T, 1}
 end