Hi, I am currently cleaning up the build of the Apache PLC4X project. We are using Asciidoctor and a lot of its plugins to generate our site. We always had to sort of double-run asciidoctor as when running as site plugin the generated content is always generated into the root project. Therefore we run the site plugin to generate the normal site content, but have it generate the images to a dummy directory of the root project. The in a second run, we have the normal asciidoctor-maven-plugin generate the normal content to a dummy directory of the current modules target and have it generate the images into the target/site directory. I now want to fix this.
The main problem is that the site configuration the asciidoctor doxia plugin uses is the one from the root of the project. The properties all also get resolved there. I tried using the lazy expansion suing @ instead of $, but all of that doesn’t work. So my question now is: Is there a way to access the MavenProject of the current module an not of the root module? Here’s the code of the thing: https://github.com/asciidoctor/asciidoctor-maven-plugin/blob/master/src/main/java/org/asciidoctor/maven/site/AsciidoctorDoxiaParser.java I would really like to fix this correctly and not fork the plugin and patch in a hack that makes it work for my usecase. Right now I am using the Doxia Sink and getting some rudimentary information from that, but it’s not a pretty solution. Chris
