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.
Let's assume I have a project depending on some external library: lib/thelib.jar, for which I have no sources. It obviously has some javadoc, but there's no clear and simple way to add this javadoc to the system. The only way is to: - add this library to the list of libraries and assign the jar & javadoc to it, - then remove automatically found lib/thelib.jar from Compiling Sources classpath; - then add the library as a library, not as a simple jar to project's Compiling Sources classpath. Not simple. And it's not project-specific. Library manager has NetBeans-wide visibility, so while I'd like to use this lib in one project only, NetBeans suggests it to be system-wide. I see usability problem here. What I'd like to see is having some tab in project properties, named "Additional Javadocs" under "General", allowing me to add additional Javadoc documentation for the project.
Interesting usecase. Why whould you prefer adding only jar file to comp. cp. of the project and then adding javadoc separatelly to creating library where you can define its cp. and javadoc and adding the whole library on the project comp. dependency? That's seems to me as easier and more straightforward solution. Re: "Library manager has NetBeans-wide visibility, so while I'd like to use this lib in one project only, NetBeans suggests it to be system-wide. I see usability problem here." What kind of usability problem you see with global list of available libraries? Nothing's forcing you to use the library somewhere else, it's just list of available libraries.
*** This issue has been marked as a duplicate of 48984 ***