In RTC Source Control w/ Eclipse client, after loading a rep workspace, .project file is an outgoing pending change. What do I do?
Hi -
First, take pity because I am just starting with RTC Source Control. Yes, I've read LOTS of things here on jazz.net. I am very experienced with ClearCase and ClearQuest, and have over 15 years CM experience.
We just started evaluating RTC w/ source control. Most of our files will be controlled via the web client. However our Java developers want to use the Eclipse client. I set up the Streams and Components. When I created (using the Eclipse client) the first repository workspace and loaded it, I accepted the incoming changes. Then there were pending outgoing changes, which only included the ".project" file. Should this file be part of the repository? I was under the impression that it worked user settings like what view was last up, etc.
If it should not be part of the repository, what do I do with the pending change? And will every user need to do this every time, or just once?
Thank you!
First, take pity because I am just starting with RTC Source Control. Yes, I've read LOTS of things here on jazz.net. I am very experienced with ClearCase and ClearQuest, and have over 15 years CM experience.
We just started evaluating RTC w/ source control. Most of our files will be controlled via the web client. However our Java developers want to use the Eclipse client. I set up the Streams and Components. When I created (using the Eclipse client) the first repository workspace and loaded it, I accepted the incoming changes. Then there were pending outgoing changes, which only included the ".project" file. Should this file be part of the repository? I was under the impression that it worked user settings like what view was last up, etc.
If it should not be part of the repository, what do I do with the pending change? And will every user need to do this every time, or just once?
Thank you!
Accepted answer
Hi Donna,
this is caused by the selection "create eclipse projects for each folder" which is marked by default when you load a workspace. Remember, you basically cannot see anything in Eclipse without it being a "project" (which is defined by the .project file).
It shouldn't harm to check it in, but if you want to get around this, you can:
1. Create an appropriate "project", "java project" or whatever you need, in your local eclipse workspace.
2. right click the component in the "pending changes" view, and select "view repository files". Then you can right click any folder on any level, and select "load" or "load as..", and then choose to load it as a sub-folder of your existing eclipse project already in your eclipse workspace BUT is NOT under RTC source control.
you can also just ignore the .project file (mentally or in the SCM ignore function), it does no harm to your files.
ps. If people are going to work with these files in eclipse, it will be WAY easier to just check in the .project file, but it will look a little ugly for other people not using eclipse.
this is caused by the selection "create eclipse projects for each folder" which is marked by default when you load a workspace. Remember, you basically cannot see anything in Eclipse without it being a "project" (which is defined by the .project file).
It shouldn't harm to check it in, but if you want to get around this, you can:
1. Create an appropriate "project", "java project" or whatever you need, in your local eclipse workspace.
2. right click the component in the "pending changes" view, and select "view repository files". Then you can right click any folder on any level, and select "load" or "load as..", and then choose to load it as a sub-folder of your existing eclipse project already in your eclipse workspace BUT is NOT under RTC source control.
you can also just ignore the .project file (mentally or in the SCM ignore function), it does no harm to your files.
ps. If people are going to work with these files in eclipse, it will be WAY easier to just check in the .project file, but it will look a little ugly for other people not using eclipse.
Comments
