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 196297 - Changes made in project meta-data remotely never get to the imported remote project
Summary: Changes made in project meta-data remotely never get to the imported remote ...
Status: RESOLVED WORKSFORME
Alias: None
Product: cnd
Classification: Unclassified
Component: Remote (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-04 13:22 UTC by Vladimir Kvashin
Modified: 2011-05-04 11:37 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Vladimir Kvashin 2011-03-04 13:22:51 UTC 
Import a remote project.
Go to remote host and change something in project properties.
These changes won't get to the shadow project.
After you save shadow project, these changes are lost in remote project.
Comment 1 Quality Engineering 2011-03-07 05:34:32 UTC 
Integrated into 'main-golden', will be available in build *201103070000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/a01ef12ac51f
User: Vladimir Kvashin <vkvashin@netbeans.org>
Log: When synchronizing back remote project, wait until all files are really uploaded to the host (fixing #196297 Changes made in project meta-data remotely never get to the imported remote project)
Comment 2 Leonid Lenyashin 2011-03-07 11:33:19 UTC 
That was never made a requirement. Setting the bar that high is not a goal. We just need to document that user need to re-import project.
Comment 3 Vladimir Kvashin 2011-03-07 16:27:17 UTC 
Yes, but once user changes a shadow project, it is synchronized back to remote, so changes that were made to remote are lost. That was the reason why I considered it a P2. Thoughts?
Comment 4 Leonid Lenyashin 2011-03-07 19:12:05 UTC 
That is better handled through a warning in case you detect a remote change (assuming you have a technology for this). Like at the moment you sync and see there is a mismatch you show a message box: "Projects are out of sync: Overwrite remote/ Re-import (overwrite local)".
BTW, it makes a lot of sense to me. Assume you have a VCS on remote host. So sometimes new version of project might be brought in at check out. In such a case user (he knows he checked out recently) will choose re-import. 
Once we have VCS support for full-remote it would be nice if the use case is automated. Beside this one I do not see any reasonable use case to address.
Comment 5 Vladimir Kvashin 2011-03-08 08:14:51 UTC 
(In reply to comment #4)
What you propose makes a lot of sense. What is absent now is this check and a possibility of re-import as update of existing shadow project.
Comment 6 Vladimir Kvashin 2011-05-04 11:37:32 UTC 
After shadow projects were removed, this is automatically fixed.