Release asciidoctor-gradle-plugin 0.8.0 about asciidoctor-gradle-plugin

[mojavelinux]

If the decision to make a 0.8.0 release is waiting for Asciidoctor 1.5.0, I just want to provide information here that I'm planning on doing the 1.5.0 release in the second week of June.

As we had discussed, if the Gradle release is going to be based on Asciidoctor 1.5.0, I recommend naming that release 1.5.0 so that we can start utilizing and aligning on semantic versions.

[mojavelinux]

I'm not opposed to releasing the Gradle plugin sooner, either as 0.8.0 or 1.5.0-beta.1 based on an AsciidoctorJ preview release.

[msgilligan]

+1

[aalmiray]

for some reason I'm OK with releasing beta and snapshots for library projects but I'm uncomfortable doing so for plugin projects (I blame maven plugins for ruining my build experience).

+1 on the rename scheme; another reason for holding back the 0.8.0 release

[msgilligan]

Grumble, grumble.

[tlberglund]

I just came up with a pretty compelling need for PDF support. How does this look right now? 0.8.0, anyone? 😀

[aalmiray]

Hi Tim, we're waiting for asciidoctor 1.5.0 to be release as it comes with built-in PDF support. @mojavelinux said that the release is imminent (no more than 2 weeks now). Once it happens you would be able to use it immediately with asciidoctor-gradle 0.7.3 as this release allows you to switch the asciidoctorj version. So what else do you need from this plugin's POV?

[tlberglund]

@aalmiray Right now, just PDFs. Of course once I start doing that, I'll be looking for docs on how to style them. I'm assuming the plugin will let me configure the location of whatever stylesheets are applicable?

[mojavelinux]

Styling PDFs is a tough nut to crack because, well, they don't understand CSS. In an attempt to make the experience at least somewhat similar to using a CSS framework like Bootstrap, I've concocted a theme data structure that, right now, is loaded from a YAML file. You can see two examples in the following folders.

https://github.com/opendevise/asciidoctor-pdf/tree/master/data/themes

For developments on the PDF converter, I recommend following the Asciidoctor PDF repo. I'm in the process of refactoring it to use the new converter API in Asciidoctor 1.5.0 so we can get it released.

https://github.com/opendevise/asciidoctor-pdf (soon to be moved under the Asciidoctor organization).

When it's done, you'll be able to convert an AsciiDoc document by simply setting the backend to "pdf". In Ruby, that would look like:

$ asciidoctor -r asciidoctor-pdf -b pdf sample.adoc

or

$ asciidoctor-pdf sample.adoc

[tlberglund]

@mojavelinux Yeah, I was expecting to have to edit some nasty style sheet. This YAML format looks nice. I've got more questions, but I'll either ask them over there or just wait for the release. 😀

[aalmiray]

We're pushing 1.5.0 in a few hours.

[mojavelinux]

Note that Asciidoctor PDF won't be supported just yet, but the Gradle plugin is ready for it. We have a blocker in the Asciidoctor PDF project that prevents it from being loaded using the standard 'require' mechanism in Ruby. That's a requirement for all Ruby-based extensions and converters to run in the AsciidoctorJ environment.

See asciidoctor/asciidoctor-pdf#29 (weekend project)