Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launch checklist #16

Closed
5 tasks done
kytrinyx opened this issue Jan 30, 2015 · 9 comments
Closed
5 tasks done

Launch checklist #16

kytrinyx opened this issue Jan 30, 2015 · 9 comments

Comments

@kytrinyx
Copy link
Member

In order to launch we should have:

  • java as a submodule in x-api
  • at least 10 problems
  • a "how to get started" topic in the help repo repo (app/pages/languages/getting-started-with-java.md)
  • one to a handful of people willing to check exercism regularly (daily?) for nitpicks to ensure that the track gets off on the right foot
  • toggle "active" to true in config.json
@kytrinyx
Copy link
Member Author

As a starting point, I have added incomplete (and wrong) documentation for how to get started: http://help.exercism.io/getting-started-with-java.html

I can't figure out what the steps are to run the tests locally.

Given that I have the exercism CLI installed (https://github.com/exercism/cli/releases/latest), and that it is configured, I want to be able to say:

exercism fetch java bob

And then follow some sort of instructions to be able to run the tests.

What files would I need to download from this repository (or elsewhere) in order to do that?

/cc @MoreNaruto @brmenchl @edrobal @chelseakomlo @charltonaustin @gitjulia @contraption

@lesterhan
Copy link

I was able to follow the instructions and run the test with "gradle test"

What I did was:

  • Install exercism via homebrew
  • Go to exercism/java/bob
  • Run "gradle test", I had 18 failed tests
  • Wrote some simple implementation, ran "gradle test" again and had 13 failed tests

@kytrinyx
Copy link
Member Author

Thanks, @contraption! I'm assuming that you have gradle in your classpath. What happens if you don't have gradle installed on your machine?

@lesterhan
Copy link

@kytrinyx Hmm, is it reasonable to include the gradle wrapper in the repo, so people can just use ./gradlew?

@pietvandongen
Copy link

I didn't have gradle installed, so when I went to ~/exercism/java/bob and ran gradle test I got:

Piets-MBP:bob pietvandongen$ gradle test
-bash: gradle: command not found

I then installed gradle with homebrew (brew install gradle) and ran the tests again, which worked perfectly!

@kytrinyx
Copy link
Member Author

@contraption it is, but I'll need to write some code in order to be able to serve it up using the exercism CLI. It's not very hard, but I have a lot on my plate at the moment.

@pietvandongen That's great! We'll also need to know how to install gradle on windows (and perhaps linux, though linux peeps tend to know how to figure that out for themselves).

@pietvandongen
Copy link

@kytrinyx Okey, here's what I did on Windows (7, 64 bit).

I first installed the exercism-cli per the website's instructions, which went smoothly. Then I did an exercism fetch java bob, which put everything in my home directory, under exercism\java\bob.

Then I went into the directory (with cmd) and typed gradle test. I got the familiar error:

'gradle' is not recognized as an internal or external command,
operable or batch file.

So I installed gradle, like so:

  • I went to http://gradle.org/installation
  • I downloaded gradle 2.2.1 (I got a big green button in the right column of the page)
  • I unpacked the ZIP file, which contained a folder (gradle-2.2.1) and copied it to a convenient location.
  • I added that location + \bin to my PATH, so I can now run gradle.

After this, I went back to my exercism\java\bob folder (still with CMD / terminal) and ran:

gradle test

This worked, I got a long trace of tests that failed and a failed build.

@kytrinyx
Copy link
Member Author

@pietvandongen Thank you! I think this is enough to get the documentation fixed, and launch the track.

@kytrinyx
Copy link
Member Author

OK, everyone! I'v updated the documentation and activated the Java track (deploying now).

I'd appreciate it if people check in regularly to help provide some feedback on people's solutions.

Since launching exercism, Haskell has been by far the most successful track. I believe that one reason for this is that there is at least one person there who makes sure that every submission receives feedback within 24 hours.

I believe a second factor of the track's success is that the feedback that is provided doesn't directly tell people what to do, but respectfully asks questions, challenging people to think about different aspects of their solution.

Thanks so much for helping get this kicked off!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants