Folders outside Eclipse - cannot get under Jazz source control
Using a fresh install of RTC 4.0.1 for Mac. I'm using Eclipse client but don't want Eclipse projects - just to control files in another folder.
I have followed https://jazz.net/library/article/192#LoadFolderOutside and https://jazz.net/library/article/531/ without success. Drag and drop into Project Explorer doesn't appear to work on a Mac.
All I have managed to do is create a stream, a repo workspace and a component. The component is listed in the Components folder but not shown "under" the repo workspace. The workspace says loaded but there are no files in it.
If I try to load the repo workspace. I just get a blank window (i.e. no file structure is shown) and the message, "No items are selected to be loaded however the repository workspace will still be shown in the Pending Changes view."
What's going wrong?
4 answers
Ok, I think I see the issue now. In order to add files to a component, you need to load the repository workspace to a local sandbox. Best approach would be to unload the repo wksp from pending changes view or the My Repository Workspaces folder in the Team Artifacts view, then Load it, choose the 3rd option "Browse the components...." -- deselect and select the component, ensure under Advanced that you have a local sandbox location specified. For the 3 Advanced options concerning the eclipse project, choose whichever you need to, but per my previous post, I always leave the default "Load and create eclipse projects...." and just ignore (a right click context menu option on files you don't want to place under version control or have pending changes track) the .project file that is created. However if you choose the 3rd option "Load the selected folders but do not...." just remember that you will not be able to interact with the file system directly through the Java perspective, you'll have to use external tools to manipulate the files but using the refresh pending changes option for the local sandbox you can have pending changes track and perform the check in and deliver/accept operations....
Comments
I believe you will need to either manually refresh the Pending Changes view so that it sees the file system you copied into the repository workspace's local sandbox. There are two types of refresh operations, the default is to refresh changes made to the server side of the repository workspace and the second is for local changes. You can click the small downward pointing arrow, just to the right of the refresh control on the pending changes view tab/title bar.
Default: Refresh remote changes
Optional: Refresh sandbox and remote changes
You can flip the default and optional with a preferences change, see below.
Window -- Preferences -- Team -- Jazz Source Control -- Changes -- Refreshing in pending changes view
In the long run having eclipse create a project for the file system shouldn't be an issue. When bringing new file systems under version control (for eclipse/java based source or even non-java source), I first load my repo workspace and have the eclipse project created for the root of the component. This let's me work within the RTC Java perspective and the package explorer. I'll even ignore the ".project" file RTC creates for the eclipse project so that RTC/Pending Changes view will not try to version those files. If you absolutely need to work external to RTC, some other IDE or directly from a file system explorer, then just make sure to refresh the pending changes view from the optional refresh above.
Default: Refresh remote changes
Optional: Refresh sandbox and remote changes
You can flip the default and optional with a preferences change, see below.
Window -- Preferences -- Team -- Jazz Source Control -- Changes -- Refreshing in pending changes view
In the long run having eclipse create a project for the file system shouldn't be an issue. When bringing new file systems under version control (for eclipse/java based source or even non-java source), I first load my repo workspace and have the eclipse project created for the root of the component. This let's me work within the RTC Java perspective and the package explorer. I'll even ignore the ".project" file RTC creates for the eclipse project so that RTC/Pending Changes view will not try to version those files. If you absolutely need to work external to RTC, some other IDE or directly from a file system explorer, then just make sure to refresh the pending changes view from the optional refresh above.
Comments
Going back to your orig post, you say that the comp is listed under the Source Control--Components folder but not your repo wksp. Try this, right click--open your repository workspace into the properties editor, (select the repo wksp and choose open), from the properties page in the middle there is a section "Components" --click--Add... and then search/select and add the component you need to that repo wksp configuration. Save the changes to the repo wksp and then reload it.
Hopefully that will sort out the issue where the comp is not listed in the load dialog above.
Hopefully that will sort out the issue where the comp is not listed in the load dialog above.
Comments
Yes, RTC can be overwhelming and some aspects are not as intuitive I agree. Don't misunderstand I wasn't implying that you should be ashamed, just that it is a shame to have you go a different direction. We certainly would rather have more people join the community than explore other solutions, but you need to find a solution that is the right fit for you and your team.
Not to imply that you have done anything incorrectly, but unless there is a technical issue with the tool (client or server side), I bet we could have gotten you through the issue if we could have put a screen sharing session together. I have been deploying to and supporting global teams with this solution for years and have never run into a situation where we couldn't get a file system imported and shared in the scm repository, sometimes it is just easier to talk and walk through it in a more direct way I suppose.
Wish I could have been of more help.
Good luck!
Not to imply that you have done anything incorrectly, but unless there is a technical issue with the tool (client or server side), I bet we could have gotten you through the issue if we could have put a screen sharing session together. I have been deploying to and supporting global teams with this solution for years and have never run into a situation where we couldn't get a file system imported and shared in the scm repository, sometimes it is just easier to talk and walk through it in a more direct way I suppose.
Wish I could have been of more help.
Good luck!