Prevent WPF files not under SCM from being deleted on Load?
Is there any way to do a "load" without existing files (not under source control) from being deleted from my project?
That is ... I create a Portlet Factory project in Eclipse. This gives me base "factory" code. Then I add files to the project as I develop my portlet. When I "check-in", the team settings in eclipse are smart enough to ignore the base portlet factory files (they don't get checked in).
But ... if someone wants to load my portlet code from RTC, they will create a portlet factory project (to get the base stuff), and then want to load my code from RTC. A "load", though, will wipe out the base portlet factory code.
Any way to avoid this? (Other than to re-add project facets ... and other project settings ... which is a bit tedious.)
Accepted answer
What you could do is use the Team-->Share Project action to hook up the
project to the corresponding remote folder. This will allow you to see
the differences between the local and remote in the Pending Changes
view. You may end up with a bunch of deletions for content that exists
remotely but not locally. If you Undo these, the content should be loaded.
Michael
P.S. I haven't tried this myself but conceptually it should work.
Comments
2 other answers
I'm curious, how did you handle this before?
Comments
what would be needed is some sort of "private" versioned file that would live in the repository workspace but not necessarily be delivered to the stream.
There where several requests for this kind of things recently. It is always interesting if one needs to be able to hold some private configuration in files that should not affect the files in the stream. Potential candidates would be server configuration files etc. that are just local but required.
Other examples could be eclipse launch files that users would want to customize for a different local setting but not share or create conflicts with the server version. Actually this is even a more mixed example where you want a versioned file in the stream but you want to be able to change it and keep the private change without affecting the common stream. This could be done manually taking care the change never gets delivered.
Ralph
I don't think there are many options, either this code is useful to others and you can un-ignore it and check it in, or you can check it in and keep it in a change set that you don't deliver. This can become tedious though.
I'm curious, how did you handle this before?
Comments
