Component names not showing in build workspace.
I have created a component with multiple sub-directories. The component is named as follows:
TC_ITK subfolders are TC_ITK->docs TC_ITK0>scr When the build engine runs the definition, it creates folders as follows: docs scr Rather than the same dir structure as I modeled in the component. I expected the build engine to build a structure where docs and scr are children of a directory TC_ITK I've tried many times to get this to work out any advice? |
11 answers
Thanks, Geoff, that did the trick. I ended up renaming the files which avoids the clash, but it looks like I can delete them now.
Use the "Browse the components to select the folders to be loaded" option for the load command, and select the component root directory itself. This will load that component as a project into the sandbox, and from there, you should be able to delete the .project file. Well, I took the plunge, created the folders & moved everything but the .project file into the new folder. I then created a new workspace and managed to get things so that I can only see one level of directory in my sandbox. However, the build extract still fails because of the .project files in each component. If I show repository files, these .project files are a peer file to the new folder I created. The thing is, I can't see those .project files in my sandbox anymore, so I can't seem to remove them from source control. The only place I can see the .project files that are peers to the new folders is in the navigator view, and team actions that would let me set these files to be ignored (or outright remove them) are not available on the navigator view. I never can see those peer .project files in the package explorer or project explorer. I've tried opening a number of different perspectives to see if there is a way to get those files to show up somewhere where I have team actions, but no luck. Any suggestions on how to clear these files out of source control now? |
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.