You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "André Fügenschuh (JIRA)" <ji...@codehaus.org> on 2009/06/05 04:21:42 UTC
[jira] Created: (MJAVADOC-236) Unable to find the javadoc version -
Windows Vista, non-privileged account
Unable to find the javadoc version - Windows Vista, non-privileged account
--------------------------------------------------------------------------
Key: MJAVADOC-236
URL: http://jira.codehaus.org/browse/MJAVADOC-236
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.5
Environment: Windows Vista SP2 (x64) - UAC enabled
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.1.0 (r755702; 2009-03-18 20:10:27+0100)
Java version: 1.6.0_14
Java home: P:\Programs\Java\jdk6\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
Reporter: André Fügenschuh
Priority: Minor
Attachments: maven-javadoc-error.txt
Plugin configuration for maven-javadoc relies on the built-in detection of the javadoc executable.
JAVA_HOME env. var. is set (system scope) to "P:/Programs/Java/jdk6"
Running 'mvn javadoc:javadoc' from a _privileged_ account runs fine, while it fails (failOnError property is true by default) when executed by a _non-privileged_ account with:
"[WARNING] Unable to find the javadoc version: Exit code: 1 - The system cannot find the path specified."
(see the attached [abridged] stacktrace)
while the javadoc executable is still found and executed - the javadoc files are generated!
BTW: Playing around with the 'javadocExecutable' and/or 'javadocVersion' property doesn't help.
--
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
[jira] Commented: (MJAVADOC-236) Unable to find the javadoc version
- Windows Vista, non-privileged account
Posted by "André Fügenschuh (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184579#action_184579 ]
André Fügenschuh commented on MJAVADOC-236:
-------------------------------------------
Yes, agreed.
Meanwhile, I found the 'real' cause, and as surefire is concerned too, I filed a new issue under MNG-4249.
> Unable to find the javadoc version - Windows Vista, non-privileged account
> --------------------------------------------------------------------------
>
> Key: MJAVADOC-236
> URL: http://jira.codehaus.org/browse/MJAVADOC-236
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Environment: Windows Vista SP2 (x64) - UAC enabled
> 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.1.0 (r755702; 2009-03-18 20:10:27+0100)
> Java version: 1.6.0_14
> Java home: P:\Programs\Java\jdk6\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> Reporter: André Fügenschuh
> Priority: Minor
> Attachments: maven-javadoc-error.txt
>
>
> Plugin configuration for maven-javadoc relies on the built-in detection of the javadoc executable.
> JAVA_HOME env. var. is set (system scope) to "P:/Programs/Java/jdk6"
> Running 'mvn javadoc:javadoc' from a _privileged_ account runs fine, while it fails (failOnError property is true by default) when executed by a _non-privileged_ account with:
> "[WARNING] Unable to find the javadoc version: Exit code: 1 - The system cannot find the path specified."
> (see the attached [abridged] stacktrace)
> while the javadoc executable is still found and executed - the javadoc files are generated!
> BTW: Playing around with the 'javadocExecutable' and/or 'javadocVersion' property doesn't help.
--
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
[jira] Closed: (MJAVADOC-236) Unable to find the javadoc version -
Windows Vista, non-privileged account
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MJAVADOC-236.
------------------------------------
Resolution: Won't Fix
This issue is more a configuration issue of your system so I close it as wont fix.
> Unable to find the javadoc version - Windows Vista, non-privileged account
> --------------------------------------------------------------------------
>
> Key: MJAVADOC-236
> URL: http://jira.codehaus.org/browse/MJAVADOC-236
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Environment: Windows Vista SP2 (x64) - UAC enabled
> 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.1.0 (r755702; 2009-03-18 20:10:27+0100)
> Java version: 1.6.0_14
> Java home: P:\Programs\Java\jdk6\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows vista" version: "6.0" arch: "amd64" Family: "windows"
> Reporter: André Fügenschuh
> Priority: Minor
> Attachments: maven-javadoc-error.txt
>
>
> Plugin configuration for maven-javadoc relies on the built-in detection of the javadoc executable.
> JAVA_HOME env. var. is set (system scope) to "P:/Programs/Java/jdk6"
> Running 'mvn javadoc:javadoc' from a _privileged_ account runs fine, while it fails (failOnError property is true by default) when executed by a _non-privileged_ account with:
> "[WARNING] Unable to find the javadoc version: Exit code: 1 - The system cannot find the path specified."
> (see the attached [abridged] stacktrace)
> while the javadoc executable is still found and executed - the javadoc files are generated!
> BTW: Playing around with the 'javadocExecutable' and/or 'javadocVersion' property doesn't help.
--
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