[ 
https://issues.apache.org/jira/browse/MJAVADOC-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957590#comment-17957590
 ] 

Olivier Lamy commented on MJAVADOC-236:
---------------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-javadoc-plugin#1006|https://github.com/apache/maven-javadoc-plugin/issues/1006].
 

> Unable to find the javadoc version - Windows Vista, non-privileged account
> --------------------------------------------------------------------------
>
>                 Key: MJAVADOC-236
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-236
>             Project: Maven Javadoc Plugin (Moved to GitHub Issues)
>          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 was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to