[jira] Commented: (MJAVADOC-28) {@link foo} doesn't work when "foo" is a package name

["Maria Odea Ching (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MJAVADOC-28?page=comments#action_60962 ] 

Maria Odea Ching commented on MJAVADOC-28:
------------------------------------------

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.

> {@link foo} doesn't work when "foo" is a package name
> -----------------------------------------------------
>
>          Key: MJAVADOC-28
>          URL: http://jira.codehaus.org/browse/MJAVADOC-28
>      Project: Maven 2.x Javadoc Plugin
>         Type: Bug

>  Environment: Windows XP
>     Reporter: Martin Desruisseaux
>     Assignee: Maria Odea Ching
>     Priority: Minor
>      Fix For: 2.0-beta-4

>
>
> 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.

-- 
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