Gerd Aschemann

I was trying to build locally and ran into this problem: [spring-propdeps-plugin-no-longer-working](https://stackoverflow.com/questions/76370197/spring-propdeps-plugin-no-longer-working)

I do have the problem as well. I am currently [trying to modularize my build](https://github.com/aim42/htmlSanityCheck/blob/1bdca7699884f5a84526d76463798dcd48136afb/.github/workflows/gradle-build.yml#L41C1-L48C1), i.e., building in one job, then upload/download artifacts including JaCoCo reports. With unmodularized builds every...

I stumbled into this very same error (and it took me some hours to come here, as I expected the problem to be sitting in front of the computer ...)....

By chance I found that you could add `baseDirFollowsSourceFile()` to the `asciidoctor` task definition to resolve this: ```groovy ... asciidoctor { ... baseDirFollowsSourceFile() ... } ... ``` Please provide at...

Right, sorry, switching to the latest asciidoctor-diagram ruby gem (1.5.3) solved the problem!

If I add the `:data-uri:` pragma to the mentioned sample or to my own adocs, I do see the following error ``` ... asciidoctor: WARNING: image to embed not found...

Could you please add a small description about the problem? I suspect it is about error messages shown in an IDE, e.g., IntelliJ (using the [IntelliJ AsciiDoctor Plugin](https://github.com/asciidoctor/asciidoctor-intellij-plugin)): and the...

If you feel my comment above describes the problem, you may assign the issue to me @gdams / @smlambert and add it to the Q1 2023 project.

Please, please don't drop AsciiDoc in favour of markdown.

I have run into the very same issue and would even consider the current behaviour as bug for two reasons * The error message does not tell you that the...