Prevent WPF files not under SCM from being deleted on Load?
Art Corl (26●4●2)
| asked Apr 28 '10, 8:53 p.m.
edited Oct 12 '17, 11:15 p.m. by David Lafreniere (4.8k●7) Is there any way to do a "load" without existing files (not under source control) from being deleted from my project?
|
Accepted answer
Michael Valenta (3.7k●3)
| answered Apr 30 '10, 10:26 a.m.
FORUM MODERATOR / JAZZ DEVELOPER edited Oct 12 '17, 11:17 p.m. by David Lafreniere (4.8k●7) What you could do is use the Team-->Share Project action to hook up the
David Lafreniere selected this answer as the correct answer
Comments I can verify Michael's suggestion - I worked with WPF development and this is the solution for working with WPF projects in RTC:
Just want to say that this isn't a problem with WPF or RTC. The key is to re-share the project to connect the new WPF project to the files already under source control. The deleting mentioned in the original post was due to loading the same project name in Eclipse (the wrong way to work in this case). Works great! I also tried the same technique with a RAD portlet/EAR project ... works!
|
2 other answers
Ralph Schoon (63.4k●3●36●46)
| answered Apr 29 '10, 10:13 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Jean-Michel,
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. Comments I'd guess there's a need to not even have the files in the repository workspace. This set of files could be quite large (as in the case of portlet factory), and really no need at all to have it in the repository.
Ralph Schoon
commented Apr 29 '10, 10:54 a.m.
| edited Oct 12 '17, 11:16 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Art,
I'd guess there's a need to not even have the files in the repository workspace. This set of files could be quite large (as in the case of portlet factory), and really no need at all to have it in the repository. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.