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 142628 - Invalid Javadoc root
Summary: Invalid Javadoc root
Status: RESOLVED DUPLICATE of bug 186723
Alias: None
Product: projects
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker with 1 vote (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-01 19:12 UTC by donpellegrino
Modified: 2010-10-21 09:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description donpellegrino 2008-08-01 19:12:18 UTC
When using Tools -> Libraries from the IDE to "Add ZIP/Folder..." to a Class Library I get the following error dialog.

"Error: Invalid Javadoc root <full path of zipfile>.  The Javadoc root does not contain the index-files folder or the 
index-all.html file."

Looking at the zipfile I am adding I find that it does have an index-all.html file but that it does not have an index-
files folder.

$ unzip -t <zipfile>

    testing: index-all.html           OK

It is unclear if the index-files folder in mandatory and therefore this zipfile is incomplete or if the error is 
misreported.  The zipfile is added to the list and the javadoc for members of this library do load as expected.  If it 
is that index-all.html OR index-files is necessary then this error is incorrect and this bug should be assigned.  If 
BOTH are necessary then I need to get the zipfile fixed and the bug should be filed as "not a bug."

Thanks.
Comment 1 ceefour 2009-02-12 19:31:05 UTC
Still happens on NetBeans 6.5, latest update.

Adding Liferay 5.2.1 Javadocs, the error happens and the docs aren't loaded at all.
Comment 2 mjr_1974 2009-04-17 18:27:48 UTC
It also happens if you want to add EasyMock javadoc...
Comment 3 Tomas Zezula 2010-10-21 09:25:51 UTC
Duplicate of already fixed issue #186723

*** This bug has been marked as a duplicate of bug 186723 ***