fopub and gradle offline mode about asciidoctor-gradle-plugin

[aalmiray]

Crazy idea: have asciidoctor-gradle include a copy of these external resources and apply a regex substitution so that the generated xml points to the local resources /cc @rwinch

[ysb33r]

If the intended switchover to prawn goes ahead, can we test that --offline works for PDF generation and as such reduce this to a non-issue?

P.S. I would be happy to help with some manual testing

[mojavelinux]

Asciidoctor PDF does not use the internet for any part of the core processing, so this will become a non-issue.

Because of the large investment in the DocBook toolchain, I do still see value in documenting how to use AsciiDoc in a documentation pipeline driven by Gradle. Keep in mind that fopub was just intended as a simple way to run the DocBook toolchain without having anything installed (e.g., ala carte, no build). In the Gradle ecosystem, it makes more sense to document how to chain together the Asciidoctor Gradle plugin with the jDocBook plugin to meet the requirement of using PDF output generated by Apache FOP.

[aalmiray]

Explicit fopub support is no longer provided by the plugin since 0.7.2

[mojavelinux]

I'll emphasize two things in support of this rejecting this issue.

First, it's important to keep in mind that the whole purpose of fopub is to run the DocBook toolchain outside of a build tool (i.e., from the commandline). When you are in Gradle, you can just use the jDocBook plugin (for reference, see the Spring Framework build). There's really no reason to support fopub in Gradle.

Second, https://www.youtube.com/watch?v=fjsSr3z5nVk

[ysb33r]

I'm cool with this.