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.
Summary: | No way to get NetBeans to use project-specific javadoc | ||
---|---|---|---|
Product: | java | Reporter: | _ mihmax <mihmax> |
Component: | Project | Assignee: | Jesse Glick <jglick> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | Keywords: | USABILITY |
Priority: | P3 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
_ mihmax
2004-11-12 11:54:45 UTC
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 *** |