Folders outside Eclipse - cannot get under Jazz source control
4 answers
Comments
Yes, I actually want to only interact with the files outside of Eclipse and use a different editor so I'll be going with the 3rd option - once I fix this :)
I agree and would follow the instructions for loading the component root in the first article linked in the question. Adding to that folder would be picked up when you perform the refresh.
Also, the command line is another option unless you don't want to deal with typing.
Tim, as I stated above, I have followed those instructions but unfortunately they do not help in my case.
The command line client. It's included in the full client zip or as a separate download in the download section.
The component root also shows for me even if the component doesn't have anything in it. I can still load the component root folder. In your screenshot, it appears that you don't have any components at all in your workspace.
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
Thanks for the reply.
Hopefully that will sort out the issue where the comp is not listed in the load dialog above.
Comments
OK, now we are getting somewhere. I did as you suggested and got a component loaded under the repo wksp. I will keep testing.
Hmm, the component is now added to the repo wksp but it doesn't seem to have any files in it. Show Repository Files returns nothing.
Without seeing exactly what you're up against, it's tough to pin point what is happening or not happening.....
Just a couple questions that may shed some light for me:
- After you loaded the repo workspace, you can now use a file system browser or other tool to browse to the local sandbox and within the component root folder, you have added new files & folders?
- Once you have confirmed that there are files and folders in the sandbox for the repo workspace, and after refreshing the sandbox and remote changes, do those newly added files/folders show up in the Pending Changes view?
- If they do show in pending changes, then they will be in the unresolved folder located underneath the tetris block looking component icon. You now should be able to perform a check-in and then the deliver operation to get the files and folders pushed up from the sandbox to the server-side repo wksp (the check-in operation) and then pushed to the stream associated with the repo wksp (the deliver operation).
- Until you perform the check-in operation, the show repository files command will not return anything, because the files and folders are in the local sandbox but not in the repository workspace on the server yet.
RTC has 3 distinct layers of isolation which is a bit different from other scm tools. The bottom layer is the sandbox (the local workspace on the users workstation/hard disk associated with the repository workspace), then the linked server-side repository workspace that catalogs all checked in versions (but is still isolated from the stream/branch), finally the last and highest layer is the stream where all team members deliver checked in change sets from their own private repository workspaces.
If you already knew the general scm concepts above, I apologize for getting into it here. I often have to get the distinction of the 3 layers across to teams that are more familiar with the traditional scm paradigm of simply checking out and checking in, having only the branch and their local workspace to contend with.
I hope this helps you in some ways. It would be a shame to see you go another direction for a solution. RTC is a really great solution with a lot of capability and features.
Everything was showing empty. In the end, I managed to get the project into RTC by first creating a general project within Eclipse, setting the project location to the folders I wanted to control and then sharing it with Jazz. Up to that point I had all sorts of issues with conflicting sandboxes, component errors and the like. I'm going to struggle on for a bit longer.
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!