Reformatted autoconf/automake template files

Moved enabling/disabling of features entirely into the autoconf script.
Use the standard --enable-* / --disable-* syntax for features, no
parsing required.  Cleaned up whitespace in Makefile.am to fit with
common practices.
Issue #20 - revised Java detection methodology

The original method of using ./configure --with-java[=javac] implies
that Java support always occurs and the caller only wants to specify
which javac implementation to use.  The preferred method is to control
enablement of the featuring using --enable-java and then separately
control any aspects of the implementation using --with-* as necessary.

So this commit makes this happen:

  --enable-java
      Enables support for the Java bindings, primarily through building
      the libopendnp3java library

Once Java support is enabled, we can now specify the path to jni.h
through four different means (choose your poison):

  JAVA_HOME="/path/to/jvm/main/tree"
      Specifies the top-level path for the Java VM files.  A typical
      default might be /usr/lib/jvm/java-7-oracle on an Ubuntu
      installation running the Oracle Java 7 VM.

  JAVAC="/path/to/jvm/bin/javac"
      Specifies the path to the javac executable located inside the Java
      VM tree.  A typical default might be
      /usr/lib/jvm/java-7-oracle/bin/javac.

  --with-javac=/path/to/jvm/bin/java
      Like specifying the JAVAC environment variable, but using an
      autoconf flag instead.

  --with-jni-include-path=/path/to/jvm/include
      Specifies the path directly to directory that contains the jni.h
      header.  A typical default might be
      /usr/lib/jvm/java-7-oracle/include.

A combination of the two sets is needed to properly enable support:

  # Assuming JAVA_HOME is set as part of your system's environment
  ./configure --enable-java

  # Overriding JAVA_HOME
  ./configure --enable-java JAVA_HOME="/usr/lib/jvm/java-7-oracle"

  # Using JAVAC and JAVA_HOME (indirectly)
  ./configure --enable-java JAVAC="${JAVA_HOME}/bin/javac"

  # Using --with-javac
  ./configure --enable-java --with-javac=${JAVA_HOME}/bin/javac

  # Using --with-jni-include-path
  ./configure --enable-java --with-jni-include-path=${JAVA_HOME}/include
Issue #19 - detect need for OPENDNP3_BOOST_TIMER_PATCH

If the Boost version is detected to be less than 1.50.0, autoconf now
adds -DOPENDNP3_BOOST_TIMER_PATCH to CPPFLAGS.
Issue #21 - build C++ demos as part of the main build effort

The binaries go to /usr/bin/dnp3-demo-* and the source goes under
/usr/share.  Eventual plan would be to also put the Java demos under
/usr/share.
Issue #19 - fixed boolean logic

CPPFLAGS was being appended in the wrong AC_COMPILE_IFELSE block
Fixed various compiler warnings shown with -Werror
Issue #21 - added pthread checks and increased compile verbosity

Checks for libpthread are needed on some systems to prevent an
"operation not permitted" error from appearing at runtime, as per
http://stackoverflow.com/questions/7359575.
Added files to support building on a Debian system

This produces two packages: libopendnp3-automatak and
libopendnp3-automatak-dev.  The first contains the actual C++ bindings
and the second contains the C++ header files needed for a wrapping
application.
Issue #22 - added support for C++ components

This change implements DEB support for libopendnp3, libopendnp3-dev, and
libopendnp3-cpp-demos.
Removing C++ demo autoconf/automake files

This functionality has been merged into the main autoconf/automake
scripts, so no reason to have a second set hanging around.
Issue #22 - added libopendnp3-java Debian package support

The C++ library that provides the JNI support is now built against the
Oracle Java 7 runtime and packaged into libopendnp3-java.

Note that on many distributions (e.g. Ubuntu), Oracle Java 7 is not used
by default so must be added explicitly.  For anyone who needs to install
the official Oracle Java 7 runtime on a Debian system, see the
following:

http://webupd8.org/2012/01/install-oracle-java-jdk-7-in-ubuntu-via.html
Issue #23 - split Java demos into separate POM containers

Maven's best practices say to use a separate POM container for each JAR,
so this is required in order to have an executable JAR per demo.
Added .gitignore to hide "target" build directories
Issue #24 - need 'addClasspath=true' in pom.xml

This appears to be a classpath issue at runtime.  The solution is to add
the 'addClasspath' tag to pom.xml.
Issue #22 - added JARs to libopendnp3-java DEB package

All JARs are now loaded to /usr/share/java for system-wide consumption.
Issue #22 - added libopendnp3-java-demos package

Split the Java demos into a separate package.
Issue #26 - made maxRequestFragmentSize public
Merge remote-tracking branch 'automatak/1.1.x'
Merge remote-tracking branch 'automatak/1.1.x'
Merge remote-tracking branch 'automatak/1.1.x'