asciidoctor/asciidoctor-maven-plugin

Optimizer fails to run on Windows

Opened this issue · 9 comments

Cattlesquat commented
  • Bug report
  • Feature request
  • Question

Description
Please see: asciidoctor/asciidoctor-pdf#1790

They fixed this in October, but that was right after your last release.

All of our maven builds are failing for all of our devs on Windows, when they get to the asciidoctor step. No amount of wrestling with paths & environment variables, etc, has been any help.

Environment information

  • asciidoctor-maven-plugin version: 2.1.0
  • asciidoctorj version: ___
  • Maven, Java and OS version:
    Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
    Maven home: C:\Users\Brian Reynolds.m2\wrapper\dists\apache-maven-3.6.3-bin\1iopthnavndlasol9gbrbg6bf2\apache-maven-3.6.3
    Java version: 15, vendor: AdoptOpenJDK, runtime: C:\Program Files\AdoptOpenJDK\jdk-15.0.0.36-hotspot
    Default locale: en_US, platform encoding: Cp1252
    OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
abelsromero commented

Have you tried overriding with the latest Asciidoctorj & jruby versions like here https://github.com/asciidoctor/asciidoctor-maven-examples/blob/70d6a34c6d2df2c94ea3206f8495c7239eb738b2/asciidoctor-pdf-example/pom.xml#L35-L45.

Not that it requires much effort, but alognside the Asciidoctorj team we try to keep things compatible so the maven-plugin can use newer versions. If the problem persists I see in the docs https://github.com/asciidoctor/asciidoctor-pdf#rghost that the path to the command can be set in an environment variable.

If none of this works, I can try to build a test, but if you can provide some reproducable with minimla instructions would help a lot.

abelsromero commented

If none of this works, I can try to build a test, but if you can provide some reproducable with minimla instructions would help a lot.

Of course if the repos are public, just feel free to point me to them too.

uckelman commented

The repo in question is here: https://github.com/vassalengine/vassal

  • 👍1
Cattlesquat commented

mvnw install -pl vassal-doc

In the repo quoted above, that's an example command that would just attempt the asciidoc part of the build.

Cattlesquat commented

I have tried various environment variable attempts such as:
set GS="C:\Program Files\gs\gs9.54.0\bin\gswin64c.exe"
With no luck, although typing %GS% at the command line with that set does launch GS

mojavelinux commented
Cattlesquat commented

Okay thanks. I guess probably asciidoc builds by our linux devs until then :D

uckelman commented

Thanks for your help. Any idea when we could expect that release?

mojavelinux commented

As soon as I can get around to wrapping up the issues. I'm likely going to push out on alpha in the new few weeks so at least there is something to start testing.

  • 👍2