Starting a new J2EE project is no simple task. There are a large number of things to consider before you start writing the code. This article details a few things to consider before you start writing the code for your project. A little bit of debate and discussion surrounding these areas can go a long ways toward solving problems later in the project and avoid potential roadblocks.
The choice of tools can make your project incredibly hard to work on or it can be a breeze. The choice of tools depends on many dynamics—not the least of which is the familiarity of the team with the tools used. Whenever I start a new J2EE project, we start by discussing which tools we want to use in the categories described in the following sections.
A solid version control system is vital to any project. The importance of the version control system increases as you start to add additional developers to the project. The best time to start using a version control system is at the very beginning of the project before the first line of code is written.
There are several very good tools out on the market today. One of my personal favorites is Subversion. Although it is a relative newcomer to the version control scene, it is quickly gaining popularity among developers. It has been coined as "CVS without the suck" by many developers in that if you know CVS, you already know most of Subversion. One of the features I like most about Subversion is that you can move items in the repository without losing your change history. For Java development, this is extremely useful.