-
Bug
-
Resolution: Unresolved
-
P4
-
None
-
21
-
generic
-
generic
ADDITIONAL SYSTEM INFORMATION :
openjdk-11, openjdk-17
A DESCRIPTION OF THE PROBLEM :
Get an error when trying to run a JAVA program or build a JAVA program from within a directory structure that as UTF characters. Seems to be similar to this problem https://www.ibm.com/support/pages/apar/IV90164.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Please follow the following instructions on Fedora 37 for accurate
``` bash
mkdir ~/Documents/befreiung-मोक्षप्राप्ति/l-𑘦𑘳𑘎𑘿𑘝𑘱𑘧𑘻𑘐
pushd ~/Documents/befreiung-मोक्षप्राप्ति/l-𑘦𑘳𑘎𑘿𑘝𑘱𑘧𑘻𑘐
git clone git@github.com:fwcd/kotlin-language-server.git
pushd kotlin-language-server
./gradlew build
```
You can also download the prebuilt binary for the same and try to run the program from within the directory path that has UNICODE characters in it as above.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The build process should run.
ACTUAL -
It runs when I run it from a ASCII encoded directory path. But with Unicode characters in the directory names, it fails.
CUSTOMER SUBMITTED WORKAROUND :
No workaround. The only workaround that I can think for is not to use UNICODE characters
FREQUENCY : always
openjdk-11, openjdk-17
A DESCRIPTION OF THE PROBLEM :
Get an error when trying to run a JAVA program or build a JAVA program from within a directory structure that as UTF characters. Seems to be similar to this problem https://www.ibm.com/support/pages/apar/IV90164.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Please follow the following instructions on Fedora 37 for accurate
``` bash
mkdir ~/Documents/befreiung-मोक्षप्राप्ति/l-𑘦𑘳𑘎𑘿𑘝𑘱𑘧𑘻𑘐
pushd ~/Documents/befreiung-मोक्षप्राप्ति/l-𑘦𑘳𑘎𑘿𑘝𑘱𑘧𑘻𑘐
git clone git@github.com:fwcd/kotlin-language-server.git
pushd kotlin-language-server
./gradlew build
```
You can also download the prebuilt binary for the same and try to run the program from within the directory path that has UNICODE characters in it as above.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
The build process should run.
ACTUAL -
It runs when I run it from a ASCII encoded directory path. But with Unicode characters in the directory names, it fails.
CUSTOMER SUBMITTED WORKAROUND :
No workaround. The only workaround that I can think for is not to use UNICODE characters
FREQUENCY : always