Upgrade to RAML Module Builder 32.x

Thank you for documenting some of the challenges you encountered

Changes has been merged into master branch.

There were some points want to mention I faced with during the process. First was related to build issue which in turn doesn't affect on build result, i.e. build was finishing successful but some odd message appeared:

org.folio.rest.tools.GenerateRunner.main() ERROR An exception occurred processing Appender STDOUT java.util.NoSuchElementException: No value present
{{ at java.base/java.util.Optional.get(Optional.java:148)}}

This has been fixed by bumping up of version of "log4j-bom" to the 2.13.3 (version of 2.11.2 was used before).

Another one was related to some kind of incompatibility of Netty library used by Vert.x 4 and java 11th - netty/netty#7769. It looks like that's known issue and it appears as unwanted messages in build log:

16:55:04 DEBUG PlatformDependent0 jdk.internal.misc.Unsafe.allocateUninitializedArray(int): unavailable
java.lang.IllegalAccessException: class io.netty.util.internal.PlatformDependent0$6 cannot access class jdk.internal.misc.Unsafe (in module java.base) because module java.base does not export jdk.internal.misc to unnamed module @41f35f7c
{{ at jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361) ~[?:?]}}

And this one has been fixed by adding manually access level for tests running plugin in pom configuration file:

<argLine>
--add-opens java.base/jdk.internal.misc=ALL-UNNAMED
-Dio.netty.tryReflectionSetAccessible=true
--illegal-access=warn
</argLine>

!image-2021-02-16-20-18-57-622.png!

Possibly all these will be useful for further moving of modules to updated versions of RMB and/or Vert.x