Update

Author: monkstone

_building/building.md

@@ -5,11 +5,11 @@ title: Building ruby-processing projects
 
 # Tools of the Trade
 
-You will need to install jdk12, maven (apache-maven-3.5+), jruby-9.2.11.0+, and have access to processing jogl jars. Note we prefer a local install of [minitest][minitest] for testing.
+You will need to install jdk11+, maven (apache-maven-3.8.3+), jruby-9.3.0.0+, and have access to processing jogl jars. Note we prefer a local install of [minitest][minitest] for testing.
 
 # How to build ruby-processing projects
 
-Install the processing so you can access the processing hacked jogl jars, unfortunately you will need to do this until the processing guys (mainly Ben Fry) see the light and convert vanilla processing to use a maven build. Do this for any other jars you require that are not available from maven central.
+You will need to get the latest version of JOGL (currently JOGL-2.4 as a release candidate)
 
 ```bash
 git clone repo

_building/hype.md

@@ -27,7 +27,7 @@ This file tells maven to do a polyglot-ruby build
   <extension>
     <groupId>io.takari.polyglot</groupId>
     <artifactId>polyglot-ruby</artifactId>
-    <version>0.4.3</version>
+    <version>0.4.6</version>
   </extension>
 </extensions>
 ```

_java/JRubyArt_propane.md

@@ -16,7 +16,7 @@ ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || !
 
 ```
 
-## AdoptOpenJDK (Recommended version 12+)
+## OpenJDK (Recommended version 11+)
 
 The development version of vanilla processing is using this version and I think it is a good choice, however to confuse matters it comes in several flavours. Vanilla processing is using the variant with a `hotspot` jvm, which is a good starting point. The ruby-processing group will be pleased to hear about anyone experimenting with the `OpenJ9` jvm.
 
@@ -34,6 +34,6 @@ The development version of vanilla processing is using this version and I think
 
 ### OpenJ9 jdk12+
 
-Is an excellent alternative (jdk14 version has been tested on linux)
+Is an excellent alternative (jdk16 version has been tested on linux)
 
 Use the latest versions of PiCrate, propane and JRubyArt to avoid reflective access warnings (you may need to define JAVA_HOME to get rid off the JRuby warnings).

_java/raspberry.md

@@ -5,17 +5,18 @@ title: Choice of JDK on Raspbian Distro
 
 # Recommended Setup For PiCrate
 
-## Raspbian Stretch Release
+## RaspbianOS Release (32 bit)
 
-The installed Oracle JDK8 probably works best, you can use the stock OpenJDK8 from Debian distribution.
+The installed OpenJDK probably just works best.
 
 ```bash
-sudo apt-get install openjdk-8-jdk
+sudo apt install openjdk-11-jdk # installs latest jdk11
 ```
 
-## Raspbian Buster Release
+## ManjaroARM (64 bit)
 
-The latest version of PiCrate works well with stock java install (jdk11) on Raspbian Buster.
+The latest version of PiCrate works well with stock java install jdk16.
 
-
-You will need to define JAVA_HOME for jdk11+ to avoid reflective access warnings with JRuby.
+```bash
+sudo pacman -S jre-openjdk
+```

_jruby/JRubyArt.md

@@ -6,7 +6,7 @@ permalink: /jruby/JRubyArt/
 
 # Recommended JRuby Install For JRubyArt
 
-The preferred JRubyArt setup requires that you do a system install of JRuby. You should install java before attempting to install JRuby. Install at least version 9.2.11.1.
+The preferred JRubyArt setup requires that you do a system install of JRuby. You should install java before attempting to install JRuby. Install at least version 9.3.0.0.
 
 # Alternative Setup For JRubyArt
 

_jruby/raspberry.md

@@ -8,18 +8,18 @@ permalink: /jruby/raspberry
 
 ## Download
 
-Download the latest JRuby release [here][download]. You could use `wget` (substituting latest version for for `9.2.11.1`):-
+Download the latest JRuby release [here][download]. You could use `wget` (substituting latest version for for `9.3.0.0`):-
 
-`wget https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.2.11.1/jruby-dist-9.2.11.1-bin.tar.gz`
+`wget https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.3.0.0/jruby-dist-9.3.0.0-bin.tar.gz`
 
 ## Install
 
 ```bash
 cd /opt
-sudo tar xzvf ~/jruby-dist-9.2.11.1-bin.tar.gz # or ~/Downloads/...
-sudo update-alternatives --install /usr/bin/jruby jruby /opt/jruby-9.2.11.1/bin/jruby 100
-sudo update-alternatives --install /usr/bin/jgem jgem /opt/jruby-9.2.11.1/bin/jgem 100
-sudo update-alternatives --install /usr/bin/jirb jirb /opt/jruby-9.2.11.1/bin/jirb 100
+sudo tar xzvf ~/jruby-dist-9.3.0.0-bin.tar.gz # or ~/Downloads/...
+sudo update-alternatives --install /usr/bin/jruby jruby /opt/jruby-9.3.0.0/bin/jruby 100
+sudo update-alternatives --install /usr/bin/jgem jgem /opt/jruby-9.3.0.0/bin/jgem 100
+sudo update-alternatives --install /usr/bin/jirb jirb /opt/jruby-9.3.0.0/bin/jirb 100
 ```
 
 ## Update
@@ -37,14 +37,14 @@ It is preferable to store gems in your local environment, if you have not instal
 1. Create local folders
 
   ```bash
-  mkdir -p ~/.gem/ruby/2.5.0
+  mkdir -p ~/.gem/ruby/2.6.0
   ```
 
 2. Set gem home/path in ~/.profile
 
   ```bash
-  echo "export GEM_HOME=\"\$HOME/.gem/ruby/2.5.0\"" >> ~/.profile
-  echo "export GEM_PATH=\"\$HOME/.gem/ruby/2.5.0\"" >> ~/.profile
+  echo "export GEM_HOME=\"\$HOME/.gem/ruby/2.6.0\"" >> ~/.profile
+  echo "export GEM_PATH=\"\$HOME/.gem/ruby/2.6.0\"" >> ~/.profile
   ```
 
   This will set were gems get installed (unless you use rvm, which would be stupid to use on raspberrypi).