[ 
http://jira.magnolia-cms.com/browse/DOCU-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21428#action_21428
 ] 

Gregory Joseph commented on DOCU-65:
------------------------------------

Ok, this is seems to only affect non-aggregated javadoc: the same class' doc in 
the aggregated javadoc is fine:
http://dev.magnolia.info/ref/4.0-rc3/apidocs/info/magnolia/cms/taglibs/SetNode.NodeMapWrapper.html

And since the superclass of SetNode.NodeMapWrapper is in {{magnolia-core}} and 
not in {{magnolia-taglib-cms}} it is not surprising the link doesn't work. The 
"only" issue here is that this should normally only prevent the javadoc tool 
from generating a link, instead of generating a bogus one.



> javadocs for nested classes contain broken links
> ------------------------------------------------
>
>                 Key: DOCU-65
>                 URL: http://jira.magnolia-cms.com/browse/DOCU-65
>             Project: Documentation
>          Issue Type: Bug
>            Reporter: Boris Kraft
>            Assignee: Gregory Joseph
>         Attachments: 
> crawl_error_sources_www_magnolia-cms_com_20090220T142241Z.csv
>
>
> For instance, 
> http://dev.magnolia.info/ref/4.0-rc3/magnolia-taglib-cms/apidocs/info/magnolia/cms/taglibs/SetNode.NodeMapWrapper.html
>  
> links of  the superclass hierarchy are wrong (try it):
> java.lang.Object
>   info.magnolia.cms.util.ContentWrapper
>       info.magnolia.cms.util.NodeMapWrapper
>           info.magnolia.cms.taglibs.SetNode.NodeMapWrapper
> Please ensure that the links in the java docs are correct.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to