|
Oracle® Application Development Framework Developer's Guide
10g Release 3 (10.1.3) B25386-01 |
|
 Previous |
 Next |
|
Oracle® Application Development Framework Developer's Guide
10g Release 3 (10.1.3) B25386-01 |
|
|
Previous |
Next |
This section contains advice for using CVS with JDeveloper generally.
Divide the development work between several projects.
Consider using a code formatter, possibly as part of an ANT build script. Build the code before checking it into CVS, and before doing a CVS update.
Consider running a continuous integration tool. The tool should rebuild the whole project whenever someone commits changes to the CVS repository, and should notify developers when code they have committed breaks the build, requesting that the code be fixed. Running a continuous integration tool will improve confidence in the quality of the code in the CVS repository, encourage developers to update more often, and lead to smaller updates and fewer conflicts.
Before importing modules, configure the CVS repository to import binary file types as binary (rather than as text), to prevent them from being corrupted.
Before clicking the Commit All button in the Pending Changes window, always refresh the contents of the window (by clicking its Refresh button) and save all files (File > Save All).
Always perform an update (Versioning > Update) or module checkout (Versioning > Check Out Module) before you start editing files, to make sure that you are working with the most recent versions.
Frequently update your code from the CVS repository.
Always add a file to CVS (using Versioning > Add) as soon as it has been created, to prevent it being deleted during an update or not uploaded during a commit.
To prevent accidental corruption of the CVS repository, do not change repository configuration files manually. If you need to change a CVS configuration file, check out CVSROOT as a module, modify the specific configuration file locally, and then commit it to the repository.
Before committing, perform a CVS update and build the code.
Commit frequently. Break up your code changes into pieces of work that can be implemented in one day. Commit when you've implemented a change.
Perform a clean update on project control files (.jpr, .jpx) that contain conflicts. It's usually easiest to take the last revision from the CVS repository and reapply your changes to the project file.
