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 225631 - files doesn't disappear in new makefile based project
Summary: files doesn't disappear in new makefile based project
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.4
Hardware: PC Solaris
: P3 normal (vote)
Assignee: Alexander Simon
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-01 12:09 UTC by soldatov
Modified: 2013-03-20 11:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
sources (10.00 KB, application/x-tar)
2013-02-01 12:09 UTC, soldatov 		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 soldatov 2013-02-01 12:09:38 UTC 
Created attachment 130926 [details]
sources

Solaris 11
NetBeans trunk (Oracle Solaris Studio dev)

test works nicely in NetBeans 7.3rc1
Scenario:
- Unpack sources
- Create makefile based project (automatic mode)
- Expand all folders in Projects tab
- Open Midnight Commander
- Move test.txt, test2.c and test3.c into other folder
- Check files in IDE
==>
expected (NB7.3): no test.txt, test2.c, test3.c
real: test.txt exist, test2.c is marked as broken, test3.c is marked as broken
- Open Midnight Commander
- Move test.txt, test2.c and test3.c into project
- Check files in IDE
==>
no changes in IDE

Workaround:
- Close project
- Open project
- Expand all folders in Projects tab
- Open Midnight Commander
- Move test.txt, test2.c and test3.c into other folder
- Check files in IDE
==> ok
- Open Midnight Commander
- Move test.txt, test2.c and test3.c into project
- Check files in IDE
==> ok
Comment 1 Alexander Simon 2013-03-20 11:03:03 UTC 
The bug was introduced during implementing new feature (see Bug #225299 Detect C/C++ specific performance problem).
This bug fixed while fixing bug #225299.
There is no separate change set that fixed this bug.