[
http://jira.codehaus.org/browse/MJAVADOC-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191332#action_191332
]
Vincent Siveton commented on MJAVADOC-263:
------------------------------------------
As described in [1], you could always specify the javadoc tool using the
javadocExecutable param, ie
{noformat}
<configuration>
<javadocExecutable>C:\jdk1.6.0\bin\javadoc.exe</javadocExecutable>
...
</configuration>
{noformat}
For other people's machines, just use env variables, ie:
{noformat}
<javadocExecutable>${env.JAVA_1.6_HOME}/bin/javadoc</javadocExecutable>
{noformat}
Does it help you?
[1]
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/examples/alternate-javadoc-tool.apt.vm
> No respect for JAVA_HOME or PATH in locating javadoc executable
> ---------------------------------------------------------------
>
> Key: MJAVADOC-263
> URL: http://jira.codehaus.org/browse/MJAVADOC-263
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
> Affects Versions: 2.6
> Reporter: Benson Margulies
>
> I have code that runs into a java 1.6 bug in javadoc, so I'm trying to be
> sure to use the 1.5 version of javadoc.
> In my .mavenrc, I set JAVA_HOME to point to 1.5. I set PATH to find a 1.5
> version of javadoc. I set my PATH in my shell to find the 1.5 version of
> Javadoc. Still, somehow, the maven-javadoc-plugin finds and runs the 1.6.0
> version.
> Command line
> was:/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/javadoc
> @options @packages
> I cannot embed a shared pathname in the POM which won't work on other
> people's machines.
--
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
