-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation modules: 'administration-guide' and 'error-references-module' fail to build on Windows #24784
Comments
escay
added a commit
to escay/glassfish
that referenced
this issue
Feb 4, 2024
ECA username 'rmisingnamesda'
arjantijms
added a commit
that referenced
this issue
Feb 5, 2024
Fixes issue #24784, cannot build doc modules on Windows
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment Details
Problem Description
mvn install
fails on Windows for two modules:Both fail the same:
With-X debugging enabled:
Steps to reproduce
Follow steps from: https://glassfish.org/pr_workflow
and run mvn install on /docs module, or on the root and wait a bit longer.
Note: problem does not occur against exactly the same source code tree but building it inside Ubuntu in WSL (version 1) on Windows.
But I do not prefer to run it in WLS, since the build performance is a bit lower.
Note: my git config is using
core.autocrlf=true
Note: "git for windows bash" locale is UTF-8:
$ locale
LANG=
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_ALL=
Impact of Issue
Cannot build documentation modules under Windows, not using "git for windows bash" and not when using cmd.exe console.
Fix
Looking for non UTF-8 characters in al *.adoc files and replacing them with an ASCII character solved the issue for me.
I did not pin it down to one exact character. I only tested administration-guide module to see if it solved the issue.
Note: there are many issues online of similar JRuby exceptions, Asciidoctor issues mention to use UTF-8 files with correct content. And that seems to work.
The text was updated successfully, but these errors were encountered: