tailieunhanh - WebSphere Studio Application Developer Version 5 Programming Guide part 77

WebSphere Studio Application Developer part 77 provides integrated development tools for all e-business development roles, including Web developers, Java developers, business analysts, architects, and enterprise programmers. The customizable, targeted, role-based approach of WebSphere Studio Application Developer will be characteristic of all new products built on the WebSphere Studio Workbench. It is well integrated with WebSphere Application Server and provides built-in server test environments that can be used for testing and profiling Web applications | As you make changes locally in your Workbench you are working isolated from the rest of the team. When you are ready to make your local resource changes available to other team members you ll need to commit your work to the branch. All such changes are classified as outgoing changes when you do a synchronization. Ideally you should update your local workspace with any changes others have made in a branch before committing your work. This ensures that you have the very latest work from the other team members. After you have updated from the branch merged any conflicting changes in your local Workbench and tested your changes locally you can more easily commit your Workbench s changes to the branch. When you commit changes to the branch your changes are copied from your local Workbench to the branch. As a result these changes are then seen as incoming changes when other developers update from the branch later. There are a few particularities that we want to point out When a repository connection is made to a CVS repository only HEAD is shown. Other branches are shown only after expanding Versions then expanding a project that uses another branch. To determine what branch a project is a part of select the project then select Properties from the context menu. Select CVS in the properties window. The Tag field shows the current branch or version. When you create a new branch the names of all existing projects in the repository show up as children of the branch node in the repository browser tree. Discarding a branch from the CVS Repositories view removes the definition from the Workbench only. The underlying CVS branch is left untouched. In the following sections we create a new branch make changes to that branch then merge the changes back with the HEAD branch. Branching Creating a branch and releasing resources to that branch is useful in cases where you are not yet ready to put your changes in the main development flow. It is also useful for creating incremental .