This feature is supported in the CVS and Visual SourceSafe integrations. There is no difference in its implementation.
For a glossary of the generic version control terms used here, please see the Version handling glossary in "Comparing files and versions" in Building Applications with JBuilder.
The Commit Browser provides meaningful status messages and context-sensitive default actions. It has three pages: the Commits page, the Summary Comment page, and the File Include Lists page.
In the Commits page, the directory tree view is in the left-hand pane and the list of files is in the right.
Select the Full List node on the left to view a list of all the files in the project displayed on the right.
Select a directory node to see a list of the files in that directory.
Click the key widget next to a directory node to expand the node.
Click a subdirectory node to see the files in a subdirectory displayed on the right.
Right-click a directory node to display a context menu that lets you perform the selected action on all of the directory's files in the list.
The context menu's options are:
Tip: If you display this context menu for the Full List node, all changed files are exposed.
The list of files is a table with three columns: Action, Status, and File Name. Action refers to the selected version control action to be performed on the file. Status refers to the file's status in version control. File Name refers to the name of the individual file to which the Status and Action options in that row apply.
Each cell in this column provides a drop-down list of options that could be used on the file, given its present version control status. JBuilder suggests a default action based on how the file achieved its present status. Click a file's cell in the Action column to view alternative actions. These vary depending on the status of the file, but No Action is always an option.
No Action simply means that no version control commands will be executed on that file. The file is not changed in any way by this command.
JBuilder makes the most sensible choices for default actions when JBuilder is used to create the file's status. For best performance in this browser, use JBuilder as the front end for your version control system. Whether you do so or not, however, you still determine the version control commands executed from this browser.
The version control status of each file is noted in the Status column of the list. These are statements of version control status only, not of how the file acheived that status.
This is the name of the file referred to in the Action and Status columns on that same row.
Select a file in the file list. The tabbed pane below the file list allows you to view the source code of the selected file in any way that's pertinent.
If you choose a file that has been changed locally, the Workspace Source, Repository Source, and Workspace Diff tabs become available. If you choose a file that has been changed on the repository, the Workspace Source, Repository Source, Repository Diff, and Complete Diff tabs become available.
Commit Browser: the Diff and Source view tabs on the Commits page
Individual Comment | This provides room for commenting on the file selected in the list of changed files. If you want to apply only the summary comment to the selected file, check the Use Summary Comment box. If you want to use both comments or the individual comment alone, uncheck this box. |
Workspace Source | This file's source code from the current workspace version. |
Repository Source | This file's source code from the current repository version. |
Workspace Diff | This file's most recent changes in your workspace. |
Repository Diff | This file's most recent changes in the repository. |
Complete Diff | Differences between the current version of this file in the repository and the current version in your workspace. This is not active in Visual SourceSafe because this integration allows only one user at a time to change a file. |
This option uses a summary comment in place of an individual comment for the selected file. Select the file then check this option to do so. Write the summary comment on the Summary Comment page. You can also apply both an individual and summary comment to the selected file from the Summary Comment page, but not from the Changes page. This is the only comment option available from this page.
The Summary Comment page provides room for a summary comment to apply to all of the changed files. The summary comment is applied ahead of any individual comments. You can apply the summary comment either in front of every individual comment, or only to files that you didn't provide an individual comment for.
To apply the summary comment to all files, check the checkbox at the bottom of the frame.
To apply the summary comment to individual files in place of an individual comment, return to the Commits page, select a file you want to apply only the summary comment to, and check the Use Summary Comment box in the Individual Comment frame at the bottom.
The File Include Lists page has two tabs: the Team Include List and the Personal Include List. These lists' defaults reflect the files placed under version control. By default, source files are automatically placed under version control, and output, resource, and backup files are not.
The File Include lists determine which files and directories can be seen in the Changes page. The Team Include List and the Personal Include List are maintained by two project files, one shared and one local. These two project files are handled behind the scenes: you see only one. JBuilder automatically sorts each piece of project information into the appropriate project file.
Return to the Changes page to click OK and exit the dialog.
The Team Include List determines which files will be shared, so before unchecking a file, make sure everyone agrees it does not need to be under version control for any reason.
This list of files is maintained by the shared project file in the repository. Maintain these settings in version control by pulling and posting the project file as needed.
The Personal Include List determines which files you will be able to see in the Changes page of this dialog. Uncheck a file or directory so it doesn't display in the Changes page. This simplifies the Changes page so it reflects only files that are of interest to you.
This list of files is maintained by the local project file, so only you can change it.