> install a servlet engine. Finally, there are Emacs packages
> for version
> controlling, but VAJ's automatic version controlling is very
> nice!
There are some problems in my opinion with VAJ's embedded version
control system, compared with CVS, for example:
1. There is really no concept of branching. You can have multiple
revisions of a class, but there is not way to branch an entire project.
2. Linked to the above, there is no automated merge capability. This
and number one make operating in an environment with highly concurrent
development streams very difficult to impossible.
3. A fundamental concept of VAJ's version control is class and package
ownership. In very large project that a single designated individual
controls access to a particular class or package is unworkable, i.e.
creates intolerable bottlenecks.
In many ways, some of which were sited, VAJ is a very productive
development environment. However, it's limited support of sophisticated
version control can be a show stopper for large development
organization, especially if they require highly concurrent development
streams.
