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 198828

Summary: Replace in files does not obey 'save to another location' project setting
Product: php Reporter: Iksa
Component: RefactoringAssignee: Petr Pisl <ppisl>
Status: RESOLVED WORKSFORME    
Severity: normal CC: mmirilovic
Priority: P2    
Version: 7.0   
Hardware: PC   
OS: Windows XP   
Issue Type: DEFECT Exception Reporter:

Description Iksa 2011-05-23 16:59:24 UTC
Have 'save to another location' set up in a PHP project's settings. Then do a 'replace in files' operation that modifies files of that PHP project.

Expected result: The modified files are copied to the location specified in the project settings.

Actual result: The modified files are saved only in the project's source file directory.

PS. I was going to check the exact name of the 'save to another location' setting, but could not do that as the IDE started to crash when I selected project properties; filed another bug about that.
Comment 1 Petr Pisl 2011-05-27 11:16:06 UTC
So if I understand correctly, you did a refactoring, the refactoring was done well, but then when you run the project, there are not the right copy in another location from the project is run. Am I right?
Comment 2 Iksa 2011-05-27 14:30:21 UTC
Yes, that is right.
Comment 3 Petr Pisl 2011-06-01 14:49:17 UTC
I have tried to reproduce it with the Rename refactoring and i'm not able to reproduce it.

Could you specify the steps?
What I did:
- invoke rename refactoring over, click on Do Refactoring in the preview window
- invoke Run action in NetBeans
Comment 4 Tomas Mysik 2011-06-01 20:12:40 UTC
Reporter, please reopen this issue and provide the steps to reproduce so we can fix it.

Thanks a lot.
Comment 5 Iksa 2011-06-02 09:37:49 UTC
Me neither was able to reproduce this any longer. Yesterday my IDE was updated, maybe that resolved the issue.
Comment 6 Marian Mirilovic 2011-06-02 09:58:53 UTC
(In reply to comment #5)
> Me neither was able to reproduce this any longer. Yesterday my IDE was updated,
> maybe that resolved the issue.

Thanks for update, so if you will face the same problem again please add requested information here and reopen. Thanks in advance.