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: | Visually distinguish compile-time from runtime module deps | ||
---|---|---|---|
Product: | apisupport | Reporter: | davidparks <davidparks> |
Component: | Project | Assignee: | Martin Kozeny <mkozeny> |
Status: | NEW --- | ||
Severity: | blocker | Keywords: | UI |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
davidparks
2008-05-16 22:54:17 UTC
reassign to project module for evaluation I've discovered that the issue is with defining a module A but making none of its packages public and then declaring module B's dependency on A. This adds module A as a run-only dependency (the build-prerequisite and compile-dependency tags are omitted). Then, declaring module A's packages public does not establish the connection. Expected behavior (from where I sit) is that the build and compile dependency is always there (even if no public packages are exposed) or that the UI will distinguish between the types of dependency the way that it does with non-Netbeans-Platform Java projects. The behavior is as designed; it is meaningless to have a compile dep on a module which does not expose any packages to you. It could be useful to specially mark the runtime-only deps (Java SE projects do not show them in Libraries at all and have a separate tab for them in Classpath). +1 to show runtime deps somewhere, probably on separate tab in Properties > Libraries. Also for test deps. If time permits. |