jxblum
commented
4 years ago I see that Spring Security is already building with Spring Build Conventions 0.0.30.RELEASE, here.
However, I don't see anything particularly interesting in the manual build.gradle nor the guides build.gradle files.
The manual build.gradle is more interesting since it is using the io.spring.conventions.docs Gradle Plugin. The guides build.gradle does not!
However, I guess the question would be, "is the Spring Security Docs Manual using the spring.css file?" I see no reason why it wouldn't apply the stylesheet unless there is some non-apparent configuration I have not come across that is excluding the CSS file in someway.
Although, the src/docs/asciidoc file structure does not contain nested "guides" unlike Spring Session core, either, as seen here.
Perhaps the guides need to be in their own sub-project/module? This is clearly the case for Spring Security, as seen here.
In any case, it is not apparent what prescribed patterns must be followed to successfully use this plugin, and specifically, the io.spring.conventions.docs Gradle Plugin.
rwinch
The
io.spring.conventions.docsGradle Plugin from Spring Build Conventions fails to resolve thespring.cssfile when building and rendering Asciidocs to HTML, EPUB, PDF, etc.When building with Gradle
6.2(or Gradle5.6.x, e.g.5.6.4), using Spring Build Conventions0.0.30.RELEASEthrows an Exception while running the Asciidoctor Gradle build task:This is the build output from Spring Session core after upgrading the Spring Build Conventions Gradle Plugin to
0.0.30.RELEASEin build.gradle.