trackler 2.1.0.53 → 2.1.0.54

data/tracks/java/POLICIES.md

@@ -17,9 +17,8 @@ Our policies are not set-in-stone. They represent directions chosen at a point i
 
 | Track Event | Policies to review |
 |:------------|:-----------------|
-| Exercise added | [Prefer instance methods](#prefer-instance-methods); [Starter implementations](#starter-implementations); [Ignore noninitial tests](#ignore-noninitial-tests) |
-| Exercise updated | [Ignore noninitial tests](#ignore-noninitial-tests); [Multiple file submissions](#multiple-file-submissions) |
-| Track order changed | [Starter implementations](#starter-implementations); [Multiple file submissions](#multiple-file-submissions) |
+| Exercise added/updated | [Prefer instance methods](#prefer-instance-methods); [Avoid using final](#avoid-using-final); [Adhere to best practices](#adhere-to-best-practices); [Starter implementations](#starter-implementations); [Ignore noninitial tests](#ignore-noninitial-tests); [Multiple file submissions](#multiple-file-submissions) |
+| Track rearranged | [Starter implementations](#starter-implementations); [Multiple file submissions](#multiple-file-submissions) |
 | New issue observed in track | [Good first patches](#good-first-patches) |
 | "Good first patch" issue completed | [Good first patches](#good-first-patches) |
 | Installing Java instructions updated | [Simple onboarding](#simple-onboarding) |
@@ -34,21 +33,24 @@ References: [[1](https://github.com/exercism/java/issues/177#issuecomment-261291
 
 ### Starter implementations
 
-> - Exercises 1-10: provide stubs for all required constructors and methods. Stubs should include the following body:
+> - Exercises 1-20: provide stubs for all required constructors and methods. Stubs should include the following body:
     `throw new UnsupportedOperationException("Delete this statement and write your own implementation.");`
-> - Exercises 11-20: provide stubs for all constructors and methods required by the first test; comment-out the bodies of any tests that require non-stubbed constructors or methods. Stubs should include the following body:
-    `throw new UnsupportedOperationException("Delete this statement and provide your own implementation.");`
-> - Exercises 21+: provide no stubs, but mention any "interesting" interface aspects in the HINTS.md file (which gets merged into the README.md for the exercise).
+> - Exercises 21+: provide no stubs by default, but either (1) add hints to the HINTS.md file (which gets merged into the README.md for the exercise) or (2) provide stubs as in exercises 1-20 for exercises that demand complicated method signatures.
 
-References: [[1](https://github.com/exercism/java/issues/178)]
+References: [[1](https://github.com/exercism/java/issues/178)], [[2](https://github.com/exercism/java/pull/683#discussion_r125506930)]
 
-### Do not make user-facing classes `final`
+### Avoid using final
 
-> Starter implementations and test classes should not include the `final` keyword in class declarations as it isn't strictly necessary and could be confusing to people unfamiliar with Java.
+> Avoid using `final` in user-facing code. Liberal use of the `final` keyword remains controversial. It adds little value to test suites, and if included in starter implementations, places implicit restrictions on user solutions.
+
+### Adhere to best practices
+
+> Ensure that all Java code adheres to the best practices listed below:
+> - minimize the accessibility of classes and members ([Effective Java, item 13](http://jtechies.blogspot.com/2012/07/item-13-minimize-accessibility-of.html))
 
 ### Ignore noninitial tests
 
-> 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).
+> All but the first test in an exercise test suite should add `@Ignore("Remove to run test")` (single test) or `@Ignore("Remove to run tests")` (parametrized test) on the line before the corresponding `@Test` annotation.
 
 References: [[1](https://github.com/exercism/java/issues/101#issuecomment-249349204)]
 

data/tracks/java/README.md

@@ -6,114 +6,4 @@ Source for Exercism Exercises in Java.
 
 For general information about how to contribute to Exercism, please refer to the [Contributing Guide](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks).
 
-## Table of Contents
-
-* [Overview](#overview)
-* [Contributing With Minimal Setup](#contributing-with-minimal-setup)
-* [Getting Familiar With the Codebase](#getting-familiar-with-the-codebase)
-  * [The `exercises` Module](#the-exercises-module)
-  * [The Problem Submodules](#the-problem-submodules)
-* [Advanced: Complete Local Setup](#advanced-complete-local-setup)
-  * [Tip: `gradle clean` before `exercism fetch`](#tip-gradle-clean-before-exercism-fetch)
-
-
-## Overview
-
-This guide covers contributing to the Java track.  If you are new, this guide is for you.
-
-If, at any point, you're having any trouble, pop in the [Gitter exercism/java room](https://gitter.im/exercism/java) or the [Gitter exercism/dev room](https://gitter.im/exercism/dev) for help.
-
-## Contributing With Minimal Setup
-
-First things first: by contributing to Exercism, you are making this learning tool that much better and improving our industry as a whole... thank you!!!
-
-To submit a fix for an existing exercise or port an exercise to Java with the least amount of setup:
-
-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/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 the [Git Basics doc](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks/git-basics.md)) to:
-   * "fork" a repository on GitHub;
-   - install `git`;
-   - "clone" a copy of your fork;
-   - 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.
-
-   The [Getting Familiar With the Codebase](#getting-familiar-with-the-codebase) section, below, is an orientation.
--  **Commit, push and create a pull request.**
-
-   Something like:
-   ```
-   $ git add .
-   $ git commit -m "(An intention-revealing commit message)"
-   $ git push
-   ```
-
-   The Git Basics doc has a section on [commit messages](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks/git-basics.md#commit-messages) that provides practical advice on crafting meaningful commit messages.
--  **Verify that your work passes all tests.**  When you create a pull request (PR), GitHub triggers a build on Travis CI.  Your PR will not be merged unless those tests pass.
-
-## Getting Familiar With the Codebase
-
-There are two objectives to the design of this build:
-
-1. when a problem is built from within the `exercism/java` repo (i.e. when you, the contributor, are developing the exercise), the tests run against the "example" code;
-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.
-
-### The `exercises` Module
-
-This is the top-level module, contained in the `exercises` directory.  It is a container for the problem sub-modules.
-
-  * its `build.gradle` points the "main" sourceset to the example code.
-  * its `settings.gradle` names each of the subprojects, one for each problem in the set.
-
-### The Problem Submodules
-
-The `exercises` subdirectory contains all of the problem submodules.
-Each problem/submodule is a subdirectory of the same name as its slug.
-
-  * its `build.gradle` names dependencies required to work that problem.
-
-Each problem/submodule has three source sets:
-
-* `src/test/java/` — a test suite defining the edges of the problem
-* `src/example/java/` — an example solution that passes all the tests
-* `src/main/java/` — starter source files, if required/desired *(this directory usually only has a `.keep` file in it)*.
-
-----
-
-## Advanced: Complete Local Setup
-
-If you are going to make significant contribution(s) to the track, you might find it handy to have a complete local install of exercism on your computer.  This way, you can run the full suite of tests without having to create/update a PR.
-
-The easiest way to achieve this is simply use the `bin/journey-test.sh` script.  However, you may want to perform other tests, depending on what you are doing.  You can do so by duplicating the setup performed by the `bin/journey-test.sh` script.
-
-### Tip: `gradle clean` before `exercism fetch`
-
-If you `exercism fetch` after doing a build, the CLI will fail with the following error message:
-
-```
-$ exercism fetch java bob
-2015/09/06 15:03:21 an internal server error was received.
-Please file a bug report with the contents of 'exercism debug' at: https://github.com/exercism/exercism.io/issues
-```
-
-and if you review the logs of your x-api, you'll find:
-
-```
-127.0.0.1 - - [06/Sep/2015:15:20:56 -0700] "GET /v2/exercises/java/bob HTTP/1.1" 500 514949 0.2138
-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 `exercism/java` repo before you fetch:
-
-```
-cd ~/workspace/exercism/java/exercises
-gradle clean
-cd ~/workspace/exercism/exercises
-exercism fetch java bob
-```
+For information on contributing to this track, refer to the [CONTRIBUTING.md](https://github.com/exercism/java/blob/master/CONTRIBUTING.md) file.

data/tracks/java/bin/README.md

@@ -0,0 +1,3 @@
+# Cross-track consistency
+
+Many of these scripts are shared between the Java and Kotlin tracks. If you make an update to a script in one of these tracks, please also update the same script in the other track if appropriate. Thank you!

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

@@ -1,10 +1,9 @@
 #!/usr/bin/env bash
 
-# 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="$TRACK"
 TRACK_SRC_EXT="java"
+CPU_CORES=`getconf NPROCESSORS_ONLN 2>/dev/null || getconf _NPROCESSORS_ONLN 2>/dev/null || echo 1`
 
 on_exit() {
   echo ">>> on_exit()"
@@ -98,6 +97,14 @@ get_cpu_architecture() {
   esac
 }
 
+get_optimal_amount_of_jobs() {
+  if [ "$CPU_CORES" -gt "1" ]; then 
+    echo $((CPU_CORES-1))
+  else 
+    echo 1 
+  fi
+}
+
 download_exercism_cli() {
   local os="$1"
   local arch="$2"
@@ -154,7 +161,7 @@ make_local_trackler() {
   local version=$( grep -m 1 'trackler' ${xapi_home}/Gemfile.lock | sed 's/.*(//' | sed 's/)//' )
 
   git checkout v${version}
-  git submodule init -- common
+  git submodule init -- problem-specifications
   git submodule update
 
   # Bake in local copy of this track; this is what we are testing.
@@ -164,7 +171,7 @@ make_local_trackler() {
   cp -r ${track_root}/exercises tracks/${TRACK}
 
   gem install bundler
-  bundle install
+  bundle install --jobs $(get_optimal_amount_of_jobs)
   gem build trackler.gemspec
 
   # Make *this* the gem that x-api uses when we build x-api.
@@ -181,7 +188,7 @@ start_x_api() {
   pushd $xapi_home
 
   gem install bundler
-  bundle install
+  bundle install --jobs $(get_optimal_amount_of_jobs) 
   RACK_ENV=development rackup &
   xapi_pid=$!
   sleep 5
@@ -269,18 +276,24 @@ main() {
 
   clean "${build_dir}"
 
-  # Make a local version of trackler that includes the source from this repo.
-  git_clone "x-api" "${xapi_home}"
-  git_clone "trackler" "${trackler_home}"
-  assert_ruby_installed "${trackler_home}"
+  # Download everything we need in parallel
+  git_clone "x-api" "${xapi_home}" &
+  git_clone "trackler" "${trackler_home}" &
+  download_exercism_cli $(get_operating_system) $(get_cpu_architecture) "${exercism_home}" &
+  wait
+
+  # Check and install the ruby stuff we need in parallel
+  assert_ruby_installed "${trackler_home}" &
+  assert_ruby_installed "${xapi_home}" &
+  wait
+
+  # Make a local version of trackler
   make_local_trackler "${trackler_home}" "${xapi_home}"
 
-  # Stand-up a local instance of x-api so we can fetch the exercises through it.
-  assert_ruby_installed "${xapi_home}"
+  # Start-up a local instance of x-api so we can fetch the exercises through it.
   start_x_api "${xapi_home}"
 
   # Create a CLI install and config just for this build; this script does not use your CLI install.
-  download_exercism_cli $(get_operating_system) $(get_cpu_architecture) "${exercism_home}"
   configure_exercism_cli "${exercism_home}" "${exercism_configfile}" "${xapi_port}"
 
   solve_all_exercises "${exercism_home}" "${exercism_configfile}"

data/tracks/java/bin/unit-tests.sh

@@ -5,11 +5,10 @@ set -e
 echo ""
 echo ">>> Running configlet..."
 bin/fetch-configlet
-bin/configlet .
+bin/configlet lint .
 
 pushd exercises
 echo ""
 echo ">>> Running tests..."
 TERM=dumb ../gradlew check compileStarterSourceJava --parallel --continue
 popd
-

data/tracks/java/config.json

@@ -284,6 +284,13 @@
 
       ]
     },
+    {
+      "slug": "spiral-matrix",
+      "difficulty": 6,
+      "topics": [
+
+      ]
+    },
     {
       "slug": "roman-numerals",
       "difficulty": 6,
@@ -301,7 +308,9 @@
     {
       "slug": "food-chain",
       "difficulty": 6,
-      "topics": []
+      "topics": [
+
+      ]
     },
     {
       "slug": "beer-song",
@@ -380,6 +389,13 @@
 
     	]
     },
+    {
+    	"slug": "bowling",
+    	"difficulty": 6,
+    	"topics": [
+
+    	]
+    },
     {
       "slug": "anagram",
       "difficulty": 7,
@@ -452,6 +468,15 @@
 
       ]
     },
+    {
+      "slug": "circular-buffer",
+      "difficulty": 8,
+      "topics": [
+        "Queues",
+        "Classes",
+        "Exception handling"
+      ]
+    },
     {
       "slug": "rectangles",
       "difficulty": 8,
@@ -474,31 +499,38 @@
       ]
     },
     {
-      "slug": "change",
+      "slug": "complex-numbers",
       "difficulty": 8,
       "topics": [
 
       ]
     },
     {
-      "slug": "palindrome-products",
+      "slug": "list-ops",
+      "difficulty": 8,
+      "topics": [
+      
+      ]
+    },
+    {
+      "slug": "change",
       "difficulty": 8,
       "topics": [
 
       ]
     },
     {
-      "slug": "pythagorean-triplet",
-      "difficulty": 9,
+      "slug": "palindrome-products",
+      "difficulty": 8,
       "topics": [
 
       ]
     },
     {
-      "slug": "list-ops",
+      "slug": "pythagorean-triplet",
       "difficulty": 9,
       "topics": [
-      
+
       ]
     },
     {

data/tracks/java/docs/RESOURCES.md

@@ -0,0 +1,6 @@
+## Useful Resources
+
+* [Stack Overflow](http://stackoverflow.com/questions/tagged/java).
+* [The Java subreddit](https://www.reddit.com/r/java)
+* [Official Java documentation](https://docs.oracle.com/javase/8/)
+* [Java Programming Books](https://github.com/vhf/free-programming-books/blob/master/free-programming-books.md#java)

data/tracks/java/exercises/accumulate/.meta/readme.go.tmpl

@@ -0,0 +1,17 @@
+# {{ .Spec.Name }}
+
+{{ .Spec.Description -}}
+{{- with .Hints }}
+{{ . }}
+{{ end }}
+{{- with .TrackInsert }}
+{{ . }}
+{{ end }}
+{{- with .Spec.Credits -}}
+## Source
+
+{{ . }}
+{{ end }}
+## Submitting Incomplete Solutions
+It's possible to submit an incomplete solution so you can see how others have completed the exercise.
+

data/tracks/java/exercises/accumulate/README.md

@@ -0,0 +1,47 @@
+# Accumulate
+
+Implement the `accumulate` operation, which, given a collection and an
+operation to perform on each element of the collection, returns a new
+collection containing the result of applying that operation to each element of
+the input collection.
+
+Given the collection of numbers:
+
+- 1, 2, 3, 4, 5
+
+And the operation:
+
+- square a number (`x => x * x`)
+
+Your code should be able to produce the collection of squares:
+
+- 1, 4, 9, 16, 25
+
+Check out the test suite to see the expected function signature.
+
+## Restrictions
+
+Keep your hands off that collect/map/fmap/whatchamacallit functionality
+provided by your standard library!
+Solve this one yourself using other basic tools instead.
+
+Lisp specific: it's perfectly fine to use `MAPCAR` or the equivalent,
+as this is idiomatic Lisp, not a library function.
+
+
+To run the tests:
+
+```sh
+$ gradle test
+```
+
+For more detailed info about the Java track see the [help page](http://exercism.io/languages/java).
+
+
+## Source
+
+Conversation with James Edward Gray II [https://twitter.com/jeg2](https://twitter.com/jeg2)
+
+## Submitting Incomplete Solutions
+It's possible to submit an incomplete solution so you can see how others have completed the exercise.
+

data/tracks/java/exercises/acronym/.meta/readme.go.tmpl

@@ -0,0 +1,17 @@
+# {{ .Spec.Name }}
+
+{{ .Spec.Description -}}
+{{- with .Hints }}
+{{ . }}
+{{ end }}
+{{- with .TrackInsert }}
+{{ . }}
+{{ end }}
+{{- with .Spec.Credits -}}
+## Source
+
+{{ . }}
+{{ end }}
+## Submitting Incomplete Solutions
+It's possible to submit an incomplete solution so you can see how others have completed the exercise.
+