-
Notifications
You must be signed in to change notification settings - Fork 11
Building
#Building Specs2 Spring from sources
If you are interested in peeking under the hood of Specs2 Spring; if you want to try to implement a new feature, you'll need to build Specs2 Spring from the sources; you might also want to set up your IDE to make it easier to write the Scala and Java code.
To build Specs2 Spring from sources, you’ll need:
- GPG to and keyset to sign the JARs. Download GPG from http://www.gnupg.org
- Paul Phillips’s SBT Extras at https://github.com/paulp/sbt-extras
- Clone of https://github.com/janm399/specs2-spring
Starting with the most user-friendly approach, install & configure GPG keychain. The details will be different, depending on your platform, but on UNIX systems, you should be able to run:
$ gpg --list-secret-keys
/Users/janmachacek/.gnupg/secring.gpg
-------------------------------------
sec 2048R/90A468A9 2012-01-30 [expires: 2016-01-30]
uid Jan Machacek <[email protected]>
ssb 2048R/A9ED23D0 2012-01-30If you cannot see any keys, you will need to generate a keypair by running gpg --gen-key. Onwards! Once you download the SBT Extras shell script, put it somewhere you remember and add it to your PATH. The common location for Specs2 Spring team at Cake Solutions is in /usr/share/scala/sbt. We also modify the PATH environment variable in /etc/profile so we can simply run sbt.
export PATH=$PATH:/usr/share/scala/sbtNext, clone the repository to some directory, say ~/Sandbox. Then you need to publish the project to your local Ivy repository.
~/Sandbox$ git clone https://github.com/janm399/specs2-spring
~/Sandbox$ cd specs2-spring
~/Sandbox/specs2-spring$ sbt publish-localAnd you’re ready to go. The "org.specs2" % "spring" % "0.7" are now available in your local Ivy repository; and you can use it in your Maven or SBT projects.
#Contributing to Specs2 Spring
If you are interested in helping out, the first thing to do is to take a look at the currently open issues at https://github.com/janm399/specs2-spring/issues and decide which one you'd like to tackle. To start making changes to the code, you'll need to fork the repository from janm399/specs2-spring to your own Github account. The clone in your account will give you read-write access. Clone your repository from Github to your machine and hack away! All Specs2 Spring authors will be delighted to help you, please contact us at "mailto:[email protected],
mailto:[email protected] or mailto:[email protected].
Follow us on twitter, too--we are https://twitter.com/#!/honzam399, https://twitter.com/#!/anirvan_cand https://twitter.com/#!/AmarettoAndCode.
When your work is done, send a pull request. We will review your code, sort out any last niggles and then merge the code into our Specs2 Spring repository. As you gain experience, we will be delighted to add you as the contributor to the main janm399/specs2-spring repository so you don't have to worry about the merge dances.