On Sun, Jul 6, 2014 at 2:18 AM, Michael <[email protected]> wrote:
> So I'm guessing that it must be something in the Gradle plugin. Getting includes working consistently across all the environments (including GitHub) is still a work in progress. The Gradle plugin presents an interesting challenge for AsciiDoc / Asciidoctor (and, in the future, the specification) because it's runs in an environment where the working directory (typically the project root) differs from the base directory (e.g., src/docs/asciidoc). The Gradle plugin has been changed a couple of times in attempt to find the right settings that allows the AsciiDoc to work both inside the Gradle project and by itself. There's an ongoing discussion about it in the issue tracker which you may want to track. https://github.com/asciidoctor/asciidoctor-gradle-plugin/issues/122 In the long run, I think the solution is that we need to split the base directory into two settings, base_dir and jail_dir. The base_dir dictates how to resolve relative paths. The jail_dir confines those paths inside a virtual file system root. If we treat the base_dir like the jail, as we are currently doing, then we are tempted to set this value to the project root, which breaks the understood behavior of include files. Cheers, -Dan -- Dan Allen | http://google.com/profiles/dan.j.allen -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
