Problems adding new files to SCM
We have created a new component and have started to add files to source control by copying them into the eclpise workspace. ie. we're not using Team>Share on an eclipse project. We are using this mechanism to do an initial import of a large group of files ~ 15K files. They then turn up in the pending changes view.
We are seeing a number of issues: a. As all of the files have come out of our old CM system, they are all read-only. RTC imports most of them ok, but it failed on about 40 of the files with access denied errors. When the read-only flag was removed from these files, they imported OK b. We were also seeing some files / directories that were ignored completely. And they didn't match any of the unchecked patterns in the eclipse client preferences Ignored resources list. What we found was that adding a pattern of 'bin' (no quotes) to the ignore list and then making sure this was unchecked made it subseqently import the content of the bin directory. So it would appear that there is perhaps an 'implicit' list of exclusions which aren't in the UI ignore list - we'd like to know what the full list of these implicit patterns is - ideally, we'd prefer that all the exclusion patterns were explicit in the UI. Any help with these would be greatly appreciated. |
2 answers
a. As all of the files have come out of our old CM system, they are all read-only. RTC imports most of them ok, but it failed on about 40 of the files with access denied errors. When the read-only flag was removed from these files, they imported OK I believe that occurs because we're trying to convert heterogeneous line endings on your commit. b. We were also seeing some files / directories that were ignored completely. And they didn't match any of the unchecked patterns in the eclipse client preferences Ignored resources list. What we found was that adding a pattern of 'bin' (no quotes) to the ignore list and then making sure this was unchecked made it subseqently import the content of the bin directory. That's an odd behavior. Eclipse tends to mark directories/files as 'derived' if they can be regenerated by the compiler. 'bin' in a project root is usually the base of the derived resources in java projects. We don't commit derived resources. It's possible that when you copied the files/folders in, the derived bit wasn't rewritten. I'm not saying that is the cause, but it's a possible cause.
RTC respects two ignore mechanisms in addition to the derived bit mentioned above: the platform ignores (available from the Preferences menu, and not shared with team members), and the jazz ignores. The jazz ignores are controlled by patterns and are kept on a per project basis. Each project has its own list, which defaults to 'bin' in project root and '*.class' anywhere in a project. See the docs for more information. If a file/directory is ignored, it won't be shown with the various jazz change decorations. You can find out why it is ignored by opening the properties of that file or folder and switching to the 'Jazz' pane in the properties window. e |
|
you say
" also some standard java project extensions may mean other things in non java developments and which are not derived objects - how do I control what is and is not ignored. Ideally I'd like a single view where I can choose what it ignores otherwise its a bit prone to people making mistakes. |
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.