Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0
-
Labels:None
-
Environment:Windows XP
-
Number of attachments :
Description
See or link tags of the kind
{@link org.mypackage}doesn't work with maven-javadoc-plugin (we get a "Tag @link: reference not found: org.mypackage" warning), while it work when using the javadoc tool from the command line or from an Ant script. I suspect that this is related to the way maven-javadoc-plugin work, which provides a list of source files as a @files argument.
A possible workaround is to provide a way to use the maven-javadoc-plugin through the javadoc's -subpackages option, instead of letting maven-javadoc-plugin creates a @files. It would gives more control to the user, would allows the current <excludePackageNames> parameter to work (this parameter is currently useless since it is ignored when the files to process are provided in @files), and would solve the problem reported in this JIRA issue.
Cannot reproduce error. When javadoc was executed, there were no warnings for the
{@link...}tags in the javadoc comments of the test project. The links were also present in the generated javadocs.