Currently, the process of building and installing bindings is quite complex.

For example, here is how to build and test Subversion and the JavaHL
bindings (from a source tarball):
1. ./configure [with some options]
2. make
3. make install
4. make check
5. make javahl
6. make javahl-tests
7. make install-javahl
8. make check-javahl

The process of building and testing the SWIG bindings is also complex
-- and it requires an entirely different set of commands from those
required to build JavaHL.

PROPOSED SOLUTION:

If the user asks configure to build a binding, build it and test it
with the rest of the Subversion.

The build process (for all bindings) will now be:
1. ./configure [with some options]
2. make
3. make install
4. make check

PROS
- The new process is simpler than the old process (half as many lines!)
- All bindings can be configured and built using the same process
(only difference is a configure option!)
- I generally expect an application to fully install after I type
"./configure [with some options] && make && make install". Subversion
will now operate as I expect.
- Other advantages?

CONS
- The new process is different from the old process (Users will have
to learn the new process)
- Other disadvantages?