jruby · Jan 27, 2016 · Jan 27, 2016 · Jan 27, 2016
Showing with 63 additions and 3 deletions.

+1 −2 .travis.yml

+61 −0 BUILDING.md

+1 −1 pom.xml
diff --git a/.travis.yml b/.travis.yml
@@ -12,8 +12,7 @@ env:
   - TEST_PROFILE=test-1.7.13
   - TEST_PROFILE=test-1.7.18
   - TEST_PROFILE=test-1.7.22
-  # fails just like 1.7.22 :
-  #- TEST_PROFILE=test-1.7.23
+  - TEST_PROFILE=test-1.7.24
   - TEST_PROFILE=test-9.0.1.0
   - TEST_PROFILE=test-9.0.4.0
 

diff --git a/BUILDING.md b/BUILDING.md
@@ -0,0 +1,61 @@
+## JRuby-OpenSSL
+
+The project is using [Maven](http://maven.apache.org/download.cgi) for build.
+
+Maven enhanced with JRuby using [Polyglot](https://github.com/takari/polyglot-maven),
+allows the build to be written using a Ruby DSL - check [*Mavenfile*](Mavenfile).
+
+If you're coming from a Ruby world and do not have Maven setup, you can alternatively
+`jruby -S gem install ruby-maven` and use the `rmvn` executable (instead of `mvn`).
+
+### Building
+
+The usual `mvn package` builds a .gem that includes the JRuby extension .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`
+
+
+### Releasing
+
+* fill in [History.md](History.md) change-log entries for release
+
+* update `VERSION` at [lib/jopenssl/version.rb](lib/jopenssl/version.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
+
+* 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`)
+
+* `git push origin master --tags`
+
+* e.g. https://github.com/jruby/jruby/commit/8750e736491825eec1d1954a07d492
+
+
+#### 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/
+```
diff --git a/pom.xml b/pom.xml
@@ -11,7 +11,7 @@ DO NOT MODIFIY - GENERATED CODE
   <modelVersion>4.0.0</modelVersion>
   <groupId>rubygems</groupId>
   <artifactId>jruby-openssl</artifactId>
-  <version>0.9.16-SNAPSHOT</version>
+  <version>0.9.16.dev-SNAPSHOT</version>
   <packaging>gem</packaging>
   <name>JRuby OpenSSL</name>
   <description>JRuby-OpenSSL is an add-on gem for JRuby that emulates the Ruby OpenSSL native library.</description>