[MJAVADOC-394] javadoc is not found properly by default under Oracle's JDK 7+ on Mac OSX

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.1
• Fix Version/s: 2.10
• Environment: Mac OSX, JDK 1.7+
• Flags: Patch
• Assignee: Herve Boutemy
• Reporter: Laird Nelson
• Created: 21/Apr/14 15:38
• Updated: 05/Apr/15 14:44
• Resolved: 08/Jun/14 04:00

Description

The logic to detect where the javadoc script is located is not correct for Oracle's JVM 1.7 and higher on Mac OSX.

The logic inside of AbstractJavadocMojo currently special-cases all JVMs running on OSX (line 3534):

AbstractJavadocMojo.java

        else if ( SystemUtils.IS_OS_MAC_OSX )
        {
            javadocExe = new File( SystemUtils.getJavaHome() + File.separator + "bin", javadocCommand );
        }

But as of JDK 1.7 as distributed by Oracle, the default "else" block should apply here (line 3538):

AbstractJavadocMojo.java

        else
        {
            javadocExe =
                new File( SystemUtils.getJavaHome() + File.separator + ".." + File.separator + "bin", javadocCommand );
        }

The solution might be to modify line 3534 as follows (or perhaps also check for Oracle's vendor string as well--anyway, you get the idea):

AbstractJavadocMojo.java

        else if ( SystemUtils.IS_OS_MAC_OSX && SystemUtils.JAVA_VERSION_FLOAT < 1.7f )
        {
            javadocExe = new File( SystemUtils.getJavaHome() + File.separator + "bin", javadocCommand );
        }

Patch forthcoming.

Issue Links

• is related to: MNG-4226 Better detection of JAVA_HOME on Apple Mac OS X
• relates to: MJAVADOC-395 Add JDK8 support to maven-javadoc-plugin