You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Martin Desruisseaux (JIRA)" <ji...@codehaus.org> on 2005/10/11 02:09:11 UTC
[jira] Created: (MNG-1166) {@link foo} doesn't work when "foo" is a package name
{@link foo} doesn't work when "foo" is a package name
-----------------------------------------------------
Key: MNG-1166
URL: http://jira.codehaus.org/browse/MNG-1166
Project: Maven 2
Type: Bug
Components: maven-javadoc-plugin
Versions: 2.0-beta-3
Environment: Windows XP
Reporter: Martin Desruisseaux
Priority: Minor
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MJAVADOC-28) {@link foo} doesn't work when "foo"
is a package name
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-28?page=all ]
Brett Porter updated MJAVADOC-28:
---------------------------------
Fix Version: 2.0
> {@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
> Priority: Minor
> Fix For: 2.0
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org