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: | False alarm when refactoring - undetected indirect dependency, shows "project X does not depend on target project Y". | ||
---|---|---|---|
Product: | java | Reporter: | pekarna <pekarna> |
Component: | Refactoring | Assignee: | Ralph Ruijs <ralphbenjamin> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 7.0.1 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
pekarna
2011-12-23 09:26:08 UTC
(In reply to comment #0) > Module A > Module B > Module C depends on B > Module D Not sure I follow what this diagram means. Is C a POM project, and if so how can it "depend" on B? A ZIP of an actual test case would be much more useful. > Now when trying to move class from D to B, NetBeans shows: > > There are references in project "D" to moved files, but source project "D" > does not depend on target project "B". Projects need not compile. Seems like the IDE is right to signal an error, just gets the wording backwards - the problem is that B does not depend on D, so any references from other classes in D might become broken by the move. Tried to reproduce the problem, but works for me in 7.1.1. Please attach a small test project with steps to reproduce. |