Warn against the use of org.asciidoctor.convert 1.5.6
See original GitHub issueplugins {
id 'org.asciidoctor.convert' version '1.5.6'
}
testCompile('org.springframework.restdocs:spring-restdocs-core:1.2.2.RELEASE')
The combination above will not replace
operation::my-example[snippets='httpie-request,http-request']
with the generated snippets.
Version 1.5.3 works.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
org.asciidoctor.convert - Gradle Plugin Portal
A Gradle plugin that uses Asciidoctor via JRuby to process AsciiDoc source files within the project.
Read more >Errors and Warnings | Asciidoctor Docs
Info messages do not stop conversion, but they indicate possible problems, and the output may not be what you were expecting. WARN (WARNING)....
Read more >Asciidoctor Gradle Plugin Suite
The Asciidoctor Gradle Plugin Suite is the official means of using Asciidoctor to convert all your AsciiDoc documentation using Gradle. This ...
Read more >asciidoctor/asciidoctorj - Gitter
If I want to log a warning, is there a logger in asciidoctorj or at least a way ... I upgraded my project...
Read more >RubyGems - asciidoctor - Versions diffs - 1.5.5 → 1.5.6 - Diffend
+ * invoke convert on result of custom inline macro if value is an inline node ... + * warn if doctype=inline is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve finally had some time to track this down. It’s a regression in the Asciidoctor Gradle plugin caused by https://github.com/asciidoctor/asciidoctor-gradle-plugin/pull/213. There’s an existing issue that is tracking the regression: https://github.com/asciidoctor/asciidoctor-gradle-plugin/issues/222. In addition to the problem occurring when using the daemon, it will also occur when using
--continuous
.Dropping back to 1.5.3 of the Asciidoctor Gradle plugin does indeed make the problem go away as @sdavids originally reported. The problem also doesn’t occur with 1.5.3 of the Gradle plugin and Asciidoctor 1.5.6.
In summary, it appears that a change in 1.5.6 of the Asciidoctor Gradle plugin interacts with something in Gradle’s daemon and triggers the problem.