Created: (MNG-4249) Environment variable with non-ASCII characters

Environment variable with non-ASCII characters
----------------------------------------------

                 Key: MNG-4249
                 URL: http://jira.codehaus.org/browse/MNG-4249
             Project: Maven 2
          Issue Type: Bug
    Affects Versions: 2.2.0
         Environment: Windows Vista SP2 (x64) - English

Java 6 (x64)
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)

Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
Java version: 1.6.0_14
Java home: P:\Programs\Java\jdk6\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"

surefire-plugin 2.4.3
javadoc-plugin 2.5

            Reporter: André Fügenschuh
            Priority: Minor
         Attachments: output.txt

This is a follow-up to MJAVADOC-236.

Running 'mvn test' or 'mvn javadoc:javadoc' generates error messages of type "The system cannot find the path specified." although tests are run successfully and javadoc files are generated.
(see the attached [abbreviated] output)

The reason is my account name that contains non-ASCII chars, e. g. 'Hömer', so the Windows environment variable %USERPROFILE% is: '%HOMEDRIVE%\Users\Hömer'.
If I change it to '%HOMEDRIVE%\Users\HMER~1' (the default '8dot3' name on Windows) all runs fine!

Steps to reproduce:
1) Create an account with non-ASCII chars, e. g. 'Hömer'
2) Run 'mvn test' and 'mvn javadoc:javadoc' on an arbitrary project
3) Look for "The system cannot find the path specified." messages.
4) set %USERPROFILE%=%HOMEDRIVE%\Users\HMER~1
6) No error messages appear.

Additional information:
- For surefire, forking must be enabled (default forkMode is 'once'), if you disable it, everything runs fine.
- I played around with changing the Windows 'codepage' used for shells (cmd.exe) from English (1252/437) to European (1250/850), without success.
- Maybe, a commonly shared component is responsible, but, as the error messages are not verbose enough (even in debug mode), I cannot figure out what, so I place the report here.

Workaround:
Set the env. var %USERPROFILE% using the '8dot3' name variant of %USERNAME%.
(I have a generic solution for setting %USERPROFILE% this way to any shell, but I don't want to go into details here; if it is of interest, I can describe it further.)



--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ http://jira.codehaus.org/browse/MNG-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196521#action_196521 ]

Gajo Csaba commented on MNG-4249:
---------------------------------

Works ok for Hömer on Windows XP with the same maven and java versions. Maybe it's a Vista bug? The Surefire plugin has this code when forkMode is once:

jvm = System.getProperty( "java.home" ) + File.separator + "bin" + File.separator + "java";

Perhaps the java.home property returns some string that is incompatible with windows. If you set log level to debug, it should write out what exactly is the value of the jvm string, like "Using JVM: blahblah"

> Environment variable with non-ASCII characters
> ----------------------------------------------
>
>                 Key: MNG-4249
>                 URL: http://jira.codehaus.org/browse/MNG-4249
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: Windows Vista SP2 (x64) - English
> Java 6 (x64)
> java version "1.6.0_14"
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
> Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
> Java version: 1.6.0_14
> Java home: P:\Programs\Java\jdk6\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> surefire-plugin 2.4.3
> javadoc-plugin 2.5
>            Reporter: André Fügenschuh
>            Priority: Minor
>         Attachments: output.txt
>
>
> This is a follow-up to MJAVADOC-236.
> Running 'mvn test' or 'mvn javadoc:javadoc' generates error messages of type "The system cannot find the path specified." although tests are run successfully and javadoc files are generated.
> (see the attached [abbreviated] output)
> The reason is my account name that contains non-ASCII chars, e. g. 'Hömer', so the Windows environment variable %USERPROFILE% is: '%HOMEDRIVE%\Users\Hömer'.
> If I change it to '%HOMEDRIVE%\Users\HMER~1' (the default '8dot3' name on Windows) all runs fine!
> Steps to reproduce:
> 1) Create an account with non-ASCII chars, e. g. 'Hömer'
> 2) Run 'mvn test' and 'mvn javadoc:javadoc' on an arbitrary project
> 3) Look for "The system cannot find the path specified." messages.
> 4) set %USERPROFILE%=%HOMEDRIVE%\Users\HMER~1
> 6) No error messages appear.
> Additional information:
> - For surefire, forking must be enabled (default forkMode is 'once'), if you disable it, everything runs fine.
> - I played around with changing the Windows 'codepage' used for shells (cmd.exe) from English (1252/437) to European (1250/850), without success.
> - Maybe, a commonly shared component is responsible, but, as the error messages are not verbose enough (even in debug mode), I cannot figure out what, so I place the report here.
> Workaround:
> Set the env. var %USERPROFILE% using the '8dot3' name variant of %USERNAME%.
> (I have a generic solution for setting %USERPROFILE% this way to any shell, but I don't want to go into details here; if it is of interest, I can describe it further.)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ http://jira.codehaus.org/browse/MNG-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196737#action_196737 ]

André Fügenschuh commented on MNG-4249:
---------------------------------------

Thanks for evaluating.

As I said "the error messages are not verbose enough (even in debug mode)" [mvn -X]:
see the attached 'output2.txt'. There's just the error message with no additional hints ...

Environment 'delta':

Java 6u16
Maven 2.2.1
javadoc-plugin 2.6.1

The paths for 'java.home' or for the used javadoc executable are valid!

> Environment variable with non-ASCII characters
> ----------------------------------------------
>
>                 Key: MNG-4249
>                 URL: http://jira.codehaus.org/browse/MNG-4249
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: Windows Vista SP2 (x64) - English
> Java 6 (x64)
> java version "1.6.0_14"
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
> Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
> Java version: 1.6.0_14
> Java home: P:\Programs\Java\jdk6\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> surefire-plugin 2.4.3
> javadoc-plugin 2.5
>            Reporter: André Fügenschuh
>            Priority: Minor
>         Attachments: output.txt, output2.txt
>
>
> This is a follow-up to MJAVADOC-236.
> Running 'mvn test' or 'mvn javadoc:javadoc' generates error messages of type "The system cannot find the path specified." although tests are run successfully and javadoc files are generated.
> (see the attached [abbreviated] output)
> The reason is my account name that contains non-ASCII chars, e. g. 'Hömer', so the Windows environment variable %USERPROFILE% is: '%HOMEDRIVE%\Users\Hömer'.
> If I change it to '%HOMEDRIVE%\Users\HMER~1' (the default '8dot3' name on Windows) all runs fine!
> Steps to reproduce:
> 1) Create an account with non-ASCII chars, e. g. 'Hömer'
> 2) Run 'mvn test' and 'mvn javadoc:javadoc' on an arbitrary project
> 3) Look for "The system cannot find the path specified." messages.
> 4) set %USERPROFILE%=%HOMEDRIVE%\Users\HMER~1
> 6) No error messages appear.
> Additional information:
> - For surefire, forking must be enabled (default forkMode is 'once'), if you disable it, everything runs fine.
> - I played around with changing the Windows 'codepage' used for shells (cmd.exe) from English (1252/437) to European (1250/850), without success.
> - Maybe, a commonly shared component is responsible, but, as the error messages are not verbose enough (even in debug mode), I cannot figure out what, so I place the report here.
> Workaround:
> Set the env. var %USERPROFILE% using the '8dot3' name variant of %USERNAME%.
> (I have a generic solution for setting %USERPROFILE% this way to any shell, but I don't want to go into details here; if it is of interest, I can describe it further.)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

     [ http://jira.codehaus.org/browse/MNG-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

André Fügenschuh updated MNG-4249:
----------------------------------

    Attachment: output2.txt

> Environment variable with non-ASCII characters
> ----------------------------------------------
>
>                 Key: MNG-4249
>                 URL: http://jira.codehaus.org/browse/MNG-4249
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: Windows Vista SP2 (x64) - English
> Java 6 (x64)
> java version "1.6.0_14"
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
> Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
> Java version: 1.6.0_14
> Java home: P:\Programs\Java\jdk6\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> surefire-plugin 2.4.3
> javadoc-plugin 2.5
>            Reporter: André Fügenschuh
>            Priority: Minor
>         Attachments: output.txt, output2.txt
>
>
> This is a follow-up to MJAVADOC-236.
> Running 'mvn test' or 'mvn javadoc:javadoc' generates error messages of type "The system cannot find the path specified." although tests are run successfully and javadoc files are generated.
> (see the attached [abbreviated] output)
> The reason is my account name that contains non-ASCII chars, e. g. 'Hömer', so the Windows environment variable %USERPROFILE% is: '%HOMEDRIVE%\Users\Hömer'.
> If I change it to '%HOMEDRIVE%\Users\HMER~1' (the default '8dot3' name on Windows) all runs fine!
> Steps to reproduce:
> 1) Create an account with non-ASCII chars, e. g. 'Hömer'
> 2) Run 'mvn test' and 'mvn javadoc:javadoc' on an arbitrary project
> 3) Look for "The system cannot find the path specified." messages.
> 4) set %USERPROFILE%=%HOMEDRIVE%\Users\HMER~1
> 6) No error messages appear.
> Additional information:
> - For surefire, forking must be enabled (default forkMode is 'once'), if you disable it, everything runs fine.
> - I played around with changing the Windows 'codepage' used for shells (cmd.exe) from English (1252/437) to European (1250/850), without success.
> - Maybe, a commonly shared component is responsible, but, as the error messages are not verbose enough (even in debug mode), I cannot figure out what, so I place the report here.
> Workaround:
> Set the env. var %USERPROFILE% using the '8dot3' name variant of %USERNAME%.
> (I have a generic solution for setting %USERPROFILE% this way to any shell, but I don't want to go into details here; if it is of interest, I can describe it further.)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

     [ http://jira.codehaus.org/browse/MNG-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MNG-4249:
-----------------------------------

    Attachment: MNG-4249.zip

I could not reproduce the issue using the attached test project and an unprivileged account called "Hömeß" on Vista, see the embedded logs for more details.

What looks interesting to me is this part of the outputs you provided:
{noformat}
[WARNING] Unable to find the javadoc version: Exit code: 1 - The system cannot find the path specified.
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)

Command line was:P:\Programs\Java\jdk6\jre\..\bin\javadoc.exe -J-version
{noformat}
Everything after the "Exit code: 1 - " till "Command line was:" is the console output of the forked process, i.e. you should be able to reproduce the message "The system cannot find the path specified" by manually executing the following command in your shell:
{noformat}
cmd.exe /X /C "P:\Programs\Java\jdk6\jre\..\bin\javadoc.exe -J-version"
{noformat}
But apparently this command only involves your shell interpreter and the Java tools. Whatever goes wrong there, is outside of the scope of Maven.

> Environment variable with non-ASCII characters
> ----------------------------------------------
>
>                 Key: MNG-4249
>                 URL: http://jira.codehaus.org/browse/MNG-4249
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: Windows Vista SP2 (x64) - English
> Java 6 (x64)
> java version "1.6.0_14"
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
> Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
> Java version: 1.6.0_14
> Java home: P:\Programs\Java\jdk6\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> surefire-plugin 2.4.3
> javadoc-plugin 2.5
>            Reporter: André Fügenschuh
>            Priority: Minor
>         Attachments: MNG-4249.zip, output.txt, output2.txt
>
>
> This is a follow-up to MJAVADOC-236.
> Running 'mvn test' or 'mvn javadoc:javadoc' generates error messages of type "The system cannot find the path specified." although tests are run successfully and javadoc files are generated.
> (see the attached [abbreviated] output)
> The reason is my account name that contains non-ASCII chars, e. g. 'Hömer', so the Windows environment variable %USERPROFILE% is: '%HOMEDRIVE%\Users\Hömer'.
> If I change it to '%HOMEDRIVE%\Users\HMER~1' (the default '8dot3' name on Windows) all runs fine!
> Steps to reproduce:
> 1) Create an account with non-ASCII chars, e. g. 'Hömer'
> 2) Run 'mvn test' and 'mvn javadoc:javadoc' on an arbitrary project
> 3) Look for "The system cannot find the path specified." messages.
> 4) set %USERPROFILE%=%HOMEDRIVE%\Users\HMER~1
> 6) No error messages appear.
> Additional information:
> - For surefire, forking must be enabled (default forkMode is 'once'), if you disable it, everything runs fine.
> - I played around with changing the Windows 'codepage' used for shells (cmd.exe) from English (1252/437) to European (1250/850), without success.
> - Maybe, a commonly shared component is responsible, but, as the error messages are not verbose enough (even in debug mode), I cannot figure out what, so I place the report here.
> Workaround:
> Set the env. var %USERPROFILE% using the '8dot3' name variant of %USERNAME%.
> (I have a generic solution for setting %USERPROFILE% this way to any shell, but I don't want to go into details here; if it is of interest, I can describe it further.)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

     [ http://jira.codehaus.org/browse/MNG-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MNG-4249.
----------------------------------

    Resolution: Not A Bug
      Assignee: Benjamin Bentmann

> Environment variable with non-ASCII characters
> ----------------------------------------------
>
>                 Key: MNG-4249
>                 URL: http://jira.codehaus.org/browse/MNG-4249
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: Windows Vista SP2 (x64) - English
> Java 6 (x64)
> java version "1.6.0_14"
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
> Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
> Java version: 1.6.0_14
> Java home: P:\Programs\Java\jdk6\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> surefire-plugin 2.4.3
> javadoc-plugin 2.5
>            Reporter: André Fügenschuh
>            Assignee: Benjamin Bentmann
>            Priority: Minor
>         Attachments: MNG-4249.zip, output.txt, output2.txt
>
>
> This is a follow-up to MJAVADOC-236.
> Running 'mvn test' or 'mvn javadoc:javadoc' generates error messages of type "The system cannot find the path specified." although tests are run successfully and javadoc files are generated.
> (see the attached [abbreviated] output)
> The reason is my account name that contains non-ASCII chars, e. g. 'Hömer', so the Windows environment variable %USERPROFILE% is: '%HOMEDRIVE%\Users\Hömer'.
> If I change it to '%HOMEDRIVE%\Users\HMER~1' (the default '8dot3' name on Windows) all runs fine!
> Steps to reproduce:
> 1) Create an account with non-ASCII chars, e. g. 'Hömer'
> 2) Run 'mvn test' and 'mvn javadoc:javadoc' on an arbitrary project
> 3) Look for "The system cannot find the path specified." messages.
> 4) set %USERPROFILE%=%HOMEDRIVE%\Users\HMER~1
> 6) No error messages appear.
> Additional information:
> - For surefire, forking must be enabled (default forkMode is 'once'), if you disable it, everything runs fine.
> - I played around with changing the Windows 'codepage' used for shells (cmd.exe) from English (1252/437) to European (1250/850), without success.
> - Maybe, a commonly shared component is responsible, but, as the error messages are not verbose enough (even in debug mode), I cannot figure out what, so I place the report here.
> Workaround:
> Set the env. var %USERPROFILE% using the '8dot3' name variant of %USERNAME%.
> (I have a generic solution for setting %USERPROFILE% this way to any shell, but I don't want to go into details here; if it is of interest, I can describe it further.)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ http://jira.codehaus.org/browse/MNG-4249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196844#action_196844 ]

André Fügenschuh commented on MNG-4249:
---------------------------------------

Okay, although annoying that we can't get this reproducible ...

FYI: as described in the OP, tests run / docs are created.

That said, commands like:

{noformat}cmd.exe /X /C "P:\Programs\Java\jdk6\jre\bin\java -jar C:\Users\HME~1\AppData\Local\Temp\surefirebooter88025.jar C:\Users\HME~1\AppData\Local\Temp\surefire88023tmp C:\Users\HME~1\AppData\Local\Temp\surefire88024tmp"{noformat}
or
{noformat}cmd.exe /X /C "P:\Programs\Java\jdk6\jre\..\bin\javadoc.exe -J-version"{noformat}

run fine!

> Environment variable with non-ASCII characters
> ----------------------------------------------
>
>                 Key: MNG-4249
>                 URL: http://jira.codehaus.org/browse/MNG-4249
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: Windows Vista SP2 (x64) - English
> Java 6 (x64)
> java version "1.6.0_14"
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
> Apache Maven 2.2.0 (r788681; 2009-06-26 15:04:01+0200)
> Java version: 1.6.0_14
> Java home: P:\Programs\Java\jdk6\jre
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> surefire-plugin 2.4.3
> javadoc-plugin 2.5
>            Reporter: André Fügenschuh
>            Assignee: Benjamin Bentmann
>            Priority: Minor
>         Attachments: MNG-4249.zip, output.txt, output2.txt
>
>
> This is a follow-up to MJAVADOC-236.
> Running 'mvn test' or 'mvn javadoc:javadoc' generates error messages of type "The system cannot find the path specified." although tests are run successfully and javadoc files are generated.
> (see the attached [abbreviated] output)
> The reason is my account name that contains non-ASCII chars, e. g. 'Hömer', so the Windows environment variable %USERPROFILE% is: '%HOMEDRIVE%\Users\Hömer'.
> If I change it to '%HOMEDRIVE%\Users\HMER~1' (the default '8dot3' name on Windows) all runs fine!
> Steps to reproduce:
> 1) Create an account with non-ASCII chars, e. g. 'Hömer'
> 2) Run 'mvn test' and 'mvn javadoc:javadoc' on an arbitrary project
> 3) Look for "The system cannot find the path specified." messages.
> 4) set %USERPROFILE%=%HOMEDRIVE%\Users\HMER~1
> 6) No error messages appear.
> Additional information:
> - For surefire, forking must be enabled (default forkMode is 'once'), if you disable it, everything runs fine.
> - I played around with changing the Windows 'codepage' used for shells (cmd.exe) from English (1252/437) to European (1250/850), without success.
> - Maybe, a commonly shared component is responsible, but, as the error messages are not verbose enough (even in debug mode), I cannot figure out what, so I place the report here.
> Workaround:
> Set the env. var %USERPROFILE% using the '8dot3' name variant of %USERNAME%.
> (I have a generic solution for setting %USERPROFILE% this way to any shell, but I don't want to go into details here; if it is of interest, I can describe it further.)

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira