The RunJava runner lags behind in a couple capabilities in part due to its requirement to avoid polluting the classpath. Additionally, it's of largely hypothetical use: a case where it's useful to run this Runtime but not run Domino's HTTP stack. Accordingly, it may very well be best to just remove it outright. Failing that, though, it could be adapted to point to a directory of JARs and build an internal URLClassLoader to avoid the necessity to shade or copy classes.
This may be obviated by https://github.com/OpenNTF/openliberty-domino/issues/72
The RunJava runner lags behind in a couple capabilities in part due to its requirement to avoid polluting the classpath. Additionally, it's of largely hypothetical use: a case where it's useful to run this Runtime but not run Domino's HTTP stack. Accordingly, it may very well be best to just remove it outright. Failing that, though, it could be adapted to point to a directory of JARs and build an internal
URLClassLoaderto avoid the necessity to shade or copy classes.