Some tips for using cvs with Jdeveloper
This is in response to a thread on OTN forums:
We’re working with 3 developers on a project, and yes jdeveloper 10.1.2 does have cvs problems, but you can learn to live with it.
Some tips:
1. Devide your work into different projects: Our workspace contains about 9 projects, and mostly we’re working in different projects.
2. Use a code formatter. We run jindent as part of our ant build script. Running the build is mandatory before checking code into cvs, and recommended before doing an cvs update.
3. Update often. I start my day by updating my code from cvs. And i do this at least 4 or 5 times per day.
4. These are the steps i take when commiting: cvs update, build, commit.
5. Commit often. Break up your code changes into pieces of work which can be implemented in one day. Commit when you’ve implemented a change. Don’t collect a weeks worth of changes before commiting.
6. Clean update .jpr/.jpx files containing conflicts. Usually it’s easiest to just take the last revision from cvs and reapply your changes to the project file.
7. Run a continous integration tool. We use cruisecontrol. Whenever someone commits changes to cvs, cruisecontrol will rebuild your complete project. If someone has commited a change which breaks the build he will be emailed, and requested to fix the code in cvs. This will improve the confidence your developers have in quality of the code in cvs, meaning that they’ll probably update more often, and have to deal will smaller updates and less conflicts.