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 125870 - Projects Don't Detect Chages in Dependent Projects
Summary: Projects Don't Detect Chages in Dependent Projects
Status: RESOLVED DUPLICATE of bug 147000
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Lahoda
URL:
Keywords:
: 134548 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-23 20:18 UTC by William Leonard
Modified: 2008-11-13 09:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Native NetBeans projects which work as expected (23.11 KB, application/octet-stream)
2008-01-24 14:00 UTC, William Leonard 		Details
Projects imported from Eclipse, which fail to recognize changes to dependent projects (4.50 KB, application/octet-stream)
2008-01-24 14:01 UTC, William Leonard 		Details
test projects (17.51 KB, application/x-compressed)
2008-02-14 14:50 UTC, Milan Kubec 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description William Leonard 2008-01-23 20:18:54 UTC 
If ProjB depends on ProjA, making a change to ProjA is not detected by ProjB until ProjA is built. I realize this is
because ProjB only knows about ProjA's jar file, however, this is a feature that Eclipse handles nicely. See
http://wiki.netbeans.org/EclipseWorkspaceImporterDemo for more details.
Comment 1 Jiri Prox 2008-01-24 08:29:19 UTC 
What type of project do you use? It works fine for me, maybe I have the projects differently configured. Can you provide
sample project?
Comment 2 William Leonard 2008-01-24 13:59:40 UTC 
Sorry, I was working with imported Eclipse projects, so this is instead a problem with the project importer. I've
attached 2 zip files, NativeNetBeansProjects.zip, which contains Proj1 and Proj2 (Proj2 depends on Proj1). Any changes
to Proj1 are properly detected by Proj2. 

I've also attached ImportedEclipseProjects.zip, which contains Proj3 and Proj4 (Proj4 depends on Proj3). In this case,
changes to Proj3 are not picked up by Proj4.
Comment 3 William Leonard 2008-01-24 14:00:29 UTC 
Created attachment 55497 [details]
Native NetBeans projects which work as expected
Comment 4 William Leonard 2008-01-24 14:01:37 UTC 
Created attachment 55498 [details]
Projects imported from Eclipse, which fail to recognize changes to dependent projects
Comment 5 Milan Kubec 2008-02-14 14:19:20 UTC 
It seems that the problem is not related to projects imported from Eclipse only. I can reproduce the same behavior in
projects directly created in NetBeans IDE. I will provide steps to reproduce.
Comment 6 Milan Kubec 2008-02-14 14:48:01 UTC 
Steps to reproduce in native netbeans projects:

- Unzip archive TestProjects.zip
- Open ProjA and ProjB and open classes TestA and TestB in editor
- Change signature of TestA.getString method, save the file
- ProjB is not marked by error badge
- Switch to TestB file in editor, error is underlined
- ProjB is still not marked by error badge
- After some time and clicking around those projects ProjB is finally marked by error
- Fix the signature of TestA.getString
- Switch to TestB file in editor, error is not there, but the project and editor tab are still badged by error
Comment 7 Milan Kubec 2008-02-14 14:50:19 UTC 
Created attachment 56684 [details]
test projects
Comment 8 Jan Lahoda 2008-02-14 15:30:00 UTC 
It is a currently known limitation that the dependencies are checked (and recompiled) only inside one source root.
Comment 9 Jan Lahoda 2008-05-12 10:42:36 UTC 
*** Issue 134548 has been marked as a duplicate of this issue. ***
Comment 10 Jan Becicka 2008-11-13 09:17:37 UTC 

*** This issue has been marked as a duplicate of 147000 ***