[MJAVADOC-547] Plugin not working if project is NOT on %SYSTEMDRIVE%

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Not A Problem
• Affects Version/s: 2.10.4, 3.0.1
• Component/s: javadoc
• Environment: Windows 7 x64 ; Apache Maven 3.5.4
• Assignee: Unassigned
• Reporter: Je Jo
• Created: 29/Nov/18 08:48
• Updated: 03/Dec/18 10:38
• Resolved: 03/Dec/18 10:38

Description

If running e.g. mvn javadoc:jar on a project stored on C: (my %SYSTEMDRIVE%) everything works as expected, i.e. the javadoc gets generated and packed into a .jar file.

If I move the project to a different drive, e.g. D: and run the same javadoc:jar goal, nothing is generated. There is no error printed to console, and the only output is

\artifact-id-of-application\target\javadoc-bundle-options\javadoc-options-javadoc-resources.xml

as you can see in the following excerpt:

 [INFO] ----------< my.package.dummy:artifact-id-of-application >-----------
 [INFO] Building Full Application Name 0.0.1-SNAPSHOT                      [5/7]
 [INFO] --------------------------------[ jar ]---------------------------------
 [INFO]
 [INFO] — maven-javadoc-plugin:3.0.1:jar (default-cli) @ artifact-id-of-application —
 [INFO]
 [INFO] --------------< my.package.dummy:dummy-distribution >---------------
 [INFO] Building Distribution Project 0.0.1-SNAPSHOT                       [6/7]
 [INFO] --------------------------------[ pom ]---------------------------------
 [INFO]
 [INFO] — maven-javadoc-plugin:3.0.1:jar (default-cli) @ dummy-distribution —
 [INFO] Not executing Javadoc as the project is not a Java classpath-capable package
 [INFO]

Can anyone reproduce this? Is this a known error?

Issue Links

• is a parent of: MJAVADOC-548 Directoryname mixed up with excludePackageNames