Adds explicit Java module descriptor

[aalmiray]

Resolves #727

Added moditect plugin in a profile guarded by a JDK activation because the plugin requires JDK9+
Tests on CI run on JDK8 and thus would cause a failure.

NOTE: This means releases must be performed with DJK9+

There was a previous configuration for the moditect plugin using en explicit module. I left in place in case you'd rather twek it instead of having the plugin create the module from scratch:

$ jarviz bytecode show --file target/json-schema-validator-1.0.80.jar 
subject: json-schema-validator-1.0.80.jar
Unversioned classes. Bytecode version: 52 (Java 8) total: 145
Versioned classes 9. Bytecode version: 53 (Java 9) total: 1

$ jarviz module descriptor --file target/json-schema-validator-1.0.80.jar 
subject: json-schema-validator-1.0.80.jar
name: com.networknt.schema
version: 1.0.80
open: false
automatic: false
exports:
  com.networknt.schema
  com.networknt.schema.format
  com.networknt.schema.uri
  com.networknt.schema.urn
  com.networknt.schema.utils
  com.networknt.schema.walk
requires:
  com.fasterxml.jackson.databind
  com.fasterxml.jackson.dataformat.yaml
  itu
  java.base mandated
  org.jruby.jcodings static
  org.jruby.joni static
  org.slf4j

[stevehu]

I didn't realize that we need to release with JDK9+. Is it possible to keep Java 8 with module support? Otherwise, I think we have to wait for the branches.

[aalmiray]

Yes, that is what ModiTect does. Compiled bytecode remains Java 8 compatible as shown by the jarviz bytecode show call. However, the ModiTect plugin requires Java 9+ to run.

[aalmiray]

Thanks! 🚀

[stevehu]

@aalmiray It works perfectly!!! I am learning new things every day. Thanks a lot. We will use Java 11 JDK for the next release.