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 127009 - Project run corrupted if project folder is renamed externally
Summary: Project run corrupted if project folder is renamed externally
Status: RESOLVED WONTFIX
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Thomas Preisler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-08 17:16 UTC by Alexander Ioffe
Modified: 2008-11-18 06:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Ioffe 2008-02-08 17:16:15 UTC
Create some sample project
Run it. It's OK
Close it.
in any external tool rename project folder
Open project again.
run it.
make OK. Run failed.
Script dorun.sh looks for OLD_PROJECT_NAME binary file
Comment 1 Thomas Preisler 2008-03-19 18:53:35 UTC
I does work for me but I can probably find cases where it wouldn't. All you would need to do though, would be to regenerate the project and rebuild it.
Comment 2 Alexander Ioffe 2008-03-26 14:21:07 UTC
Build 2008_03_24
Bug is present.
May be this scenario is not correct absolutely.
User should copy project via IDE. Not in console.
But user may do this.

Also there is a workaround:
Go to Project properties | Linker
Output property.
remove it and press Enter. IDE will regenerate it and Run becomes OK.
So, because of workaround I will reduce it to P4. 
But may be we should add this bug to known bugs
Comment 3 Thomas Preisler 2008-11-18 05:59:35 UTC
Now I know what is going on. The default name of the executable is derived from the base name (name of project folder). You can build and run a project and 
it will build the default name and run the default name but not store it. If you then manually rename the project folder the project keeps it original name but 
it will try and execute the (new) default name that doesn;t exist. All you will need to do is to clean & build and it will use new default name.

It is not really a bug but could be 'fixed' by deriving the name of the executable from the project name rather than the project folder. Not sure I will do that 
because it may have other implications.
Comment 4 Thomas Preisler 2008-11-18 06:01:48 UTC
I should add that the project is *not* corrupted. It is healthy and in fine shape. All you need to do is to clean & build.