That's fantastic, only one question, I know that for example @lincolnthree in https://github.com/asciidoctor/asciidoctorj/issues/102 tried to run at JBoss asciidoctor (I don't know all the details) but he needed to extract gems from jar and load them as load path, if not then an exception of JRuby noticing that "asciidoctor gem is not available" was thrown. In your integration to WildFly I think it is not required this anymore. Is it true? Maybe this happens because Asciidoctor is a module on his own, meanwhile if you trying to use it directly inside your application then the classpath issues appear.