[chore] update BUILDING guide

Author: kares

BUILDING.md

@@ -10,15 +10,19 @@ If you're coming from a Ruby world and do not have Maven setup, you can alternat
 
 ### Building
 
-The usual `mvn package` builds a .gem that includes the JRuby extension .jar
+The usual `./mvnw package -Dmaven.test.skip=true` builds a .gem that includes the JRuby extension .jar
 
+There's a rake target as well that shells out: `jruby -S rake jar`
 
 ### Testing
 
-Tests `mvn test` are run by default with Maven using JRuby plugins.
-When the ext .jar is build (`rake jar` or `mvn package -Dmaven.test.skip=true`)
-one can run a tests Ruby-style e.g. `jruby -Ilib:. src/test/ruby/test_bn.rb`
+NOTE: the ext .jar needs to be build (see the Building section above on `rake jar`)
 
+The full unit test suite can be boostraped using Rake: `jruby -S rake test`
+
+Tests can also be run individually e.g. `jruby -Ilib:src/test/ruby src/test/ruby/test_bn.rb`
+
+NOTE: make sure to **-Ilib** otherwise you end up using the OpenSSL default gem shipped with JRuby.
 
 ### Releasing
 
@@ -28,39 +32,13 @@ one can run a tests Ruby-style e.g. `jruby -Ilib:. src/test/ruby/test_bn.rb`
   make sure [pom.xml](pom.xml) is regenerated e.g. using `rmvn validate`
   and `git commit` the changes
 
-* (optional) signing artifacts is preferred thus find your GPG key
-
-* `mvn -Prelease -DupdateReleaseInfo=true -Dgpg.keyname=A7A374B9 clean deploy`
-
-* (advised) examine and close the repository to push it to Sonatype's staging
-
-* (advised) run JRuby's full suite using the staged new jruby-openssl gem
-  e.g. https://github.com/jruby/jruby/commit/1df6315e9145195f19ad862be5e3a5
-
-* (advised) release the staging repository at Sonatype's if all is well
-
-* (optional) update JRuby to bundle new jruby-openssl gem (remove staging)
-  e.g. https://github.com/jruby/jruby/commit/8750e736491825eec1d1954a07d492
+* `mvn -Prelease -DupdateReleaseInfo=true clean package`
 
 * gem push the build gem from pkg/ e.g. `gem push pkg/jruby-openssl-0.9.15.gem`
 
 * tag the release e.g. `git tag v0.9.15`
 
 * update `VERSION` to next SNAPSHOT (e.g. `"0.9.16.dev"`) and commit
-  make sure [pom.xml](pom.xml) is regenerated (`rmvn validate`)
+  make sure [pom.xml](pom.xml) is regenerated (`./mvnw validate`)
 
 * `git push origin master --tags`
-
-* (advised) ... take the rest of the day off!
-
-
-#### Manually Deploying
-
-When a release went by only pushing to http://rubygems.org/ one can still push
-to Sonatype's Maven repos, rename *jruby-openssl-x.x.x-java.gem* (when it is
-downloaded from https://rubygems.org/gems/jruby-openssl) to follow Maven's
-naming conventions (stripping the *-java* suffix) and "mvn deploy" by hand :
-
-```
-mvn deploy:deploy-file -Dfile=jruby-openssl-0.9.15.gem -DpomFile=pom.xml -DrepositoryId=ossrh -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/
-```