This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 62086 - Broken links in javadoc
Summary: Broken links in javadoc
Status: VERIFIED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks: 62058
  Show dependency tree
 
Reported: 2005-08-10 16:28 UTC by Marian Mirilovic
Modified: 2007-09-26 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
broken links (622 bytes, text/plain)
2005-08-10 16:29 UTC, Marian Mirilovic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2005-08-10 16:28:30 UTC
Please fix broken links in javadoc (see attachment - sources from sources
09/08/2005 ).
For more details see issue 62058.
Comment 1 Marian Mirilovic 2005-08-10 16:29:12 UTC
Created attachment 23672 [details]
broken links
Comment 2 Jan Becicka 2005-08-11 10:39:02 UTC

*** This issue has been marked as a duplicate of 62107 ***
Comment 3 Marian Mirilovic 2005-08-17 08:49:04 UTC
this isn't dup of issue 62107, look at the attachment 
Comment 4 Martin Matula 2005-08-19 18:17:43 UTC
Seems to happen due to the fact that the javadoc infrastructure tries to be too
smart and automatically generates links to javadoc of modules that do not have
any (e.g. javax.jmi.reflect). I don't see this described anywhere. I don't know
how to fix this. Reassigning to nbbuild.
Comment 5 Jesse Glick 2005-08-19 22:09:54 UTC

*** This issue has been marked as a duplicate of 62090 ***
Comment 6 Jaroslav Tulach 2005-08-25 17:57:06 UTC
This is very likely not duplicate. As described in issue 62090 I have added 
the description of what to do with <defaultanswer/>.  I have updated the docs:    
http://www.netbeans.org/source/browse/openide/www/tutorial/api.html?r1=1.48&r2=1.49    
So I believe there is a way to fix the problem on your side.    
 
Comment 7 Martin Matula 2005-08-25 18:36:38 UTC
This was fixed together with issue 62090.
Comment 8 Marian Mirilovic 2005-08-26 12:32:39 UTC
verified in NB.dev(200508251800)
Comment 9 Quality Engineering 2007-09-20 12:01:37 UTC
Reorganization of java component