Posted by glaforge on Oct 08, 2013; 10:19am
URL: https://discuss.asciidoctor.org/Breaking-changes-with-0-1-4-tp757.html

Hi all,

I'm using Asciidoctor through the Asciidoctor Gradle plugin.
I was using version 0.5.0 of the plugin which used the previous version of Asciidoctor, but I decided to try the latest version, 0.6.0, that Andrés has just released, and which is using Asciidoctor 0.1.4.
There are a few very interesting features I'm longing to try and integration for the Groovy documentation :-)

But alas, I'm encountering some issues...

In a nutshell, here's the log of my build after the upgrade:
http://rifers.org/paste/show/2350

The tons of warnings seem to be related to includes.
It seems somehow the default base path, or something like that, has changed?
Or is it something specific to the Gradle plugin?

I'm using includes like this:

[source,groovy]
----
include::../test/SyntaxTest.groovy[tags=hexadecimal_literal_example,indent=0]
----

Basically, it's a relative path, ie. relative to my core-syntax.adoc file doing the above include.

But instead of resolving the fully qualified path to:
/Users/glaforge/Projects/groovy/groovy-git/src/spec/test/SyntaxTest.groovy

It's resolved instead to :
/Users/glaforge/Projects/groovy/test/SyntaxTest.groovy

So it seems somehow now that the relative path is resolved against the root of the project, rather than relative to the document.
Issue with Asciidoctor or with the plugin?

And the other issue I'm seeing in the build log is this serialization issue with JRuby:
java.io.NotSerializableException: org.jruby.Ruby

It's the big stacktrace at the end of the logs.

It might also be related to the Gradle plugin though, as it seems that it's Gradle trying to somehow serialize it:

org.gradle.api.UncheckedIOException: Could not add entry ':asciidoctor' to cache taskArtifacts.bin (/Users/glaforge/Projects/groovy/groovy-git/.gradle/1.7/taskArtifacts/taskArtifacts.bin).

Any hint will be most welcome :-)

Guillaume