fix relative path in project export files

The earlier commit 6d07ec56bc83c3e1e085ec33cec089bc49595f07 already fixed
relative paths in export files for package export; this commit does the same
for project export files.

See Trilinos bug #6181.
add basic travis-ci file
do out-of-source build
travis-ci: add fortran compiler
Adding some vertical whitespace to standardized formatting
Fixing nasty bug where TriBITS checkin-test.py config used instead of project's (TriBITS #5)

As explained in the TriBITS Github issue #5, The TriBITS checkin-test.py
configuration was always getting used instead of the proejct's configuration
file.  This was caused by the commit:

  5c2aa1d "Allow for usage of the checkin-test.py script for TriBITS itself."
  Author: Roscoe A. Bartlett <bartlettra@ornl.gov>
  Date:   Fri Sep 5 15:58:24 2014 -0400 (4 days ago)

  A       project-checkin-test-config.py

which exposed a latent defect added way back when TriBITS was first split off
from Trilinos. The problem was that the base directory for the found
<projectDir>/project-checkin-test-config.py was append *not* prepended to
sys.path before including the module with:

    __import__(moduleName).configuration

This was very bad becuase the TriBITS base path automatically gets *prepended*
by python into sys.path just by the checkin-test.py script running the
checkin-test.py script.  Therefore, when I added the file:

   TriBITS/project-checkin-test-config.py

which got snapshotted to:

   Trilinos/cmake/tibits/project-checkin-test-config.py

this logic resulted in this file getting selected for the project's
checkin-test.py configuration file, not the project's:

   Trilinos/project-checkin-test-config.py

file.

By picking up the TriBITSProj project's project-checkin-test-config.py file,
it got --enable-packages=TriBITS and also ignore all of the other
Trilinos-specific MPI_DEBUG and SERIAL_RELEASE options.  Very bad.

Also, as part of this commit, I figured out how to set the default for
--src-dir to the same directory where the project's
project-checkin-test-config.py is found.  That means that checkin-test.py will
automatically pick up the projects project-checkin-test-config.py file as long
as the checkin-test.py script is symlinked into the project's base directory
tree, no matter where it get TriBITS from.  This also allows the
checkin-test.py script under the TriBITSProj build to automatically find the
right project directory.

This is really a great commit if you take this all in!

For GitHub: Fixes #5
Adding all checkin-test.py defaults to config file and removing checkin-test.py (Trilinos #6218)

Now that checkin-test.py will correctly pick up --src-dir given the localtion
of the found project-checkin-test-config.py in the base directory, there is no
longer any reason to have a generic checkin-test.sh wrapper.  Therefore, I
have added the defaults --no-rebase --no-append-test-results directly to the
TriBITSProj project's configuration file.

Now you can push to TriBITS by directly calling the checkin-test.py script and
not bother with a wrapper script.  That will work fine as long as the
compilers and MPI are in your default path.
Merge remote branch 'nico-github/travis_ci'
Merge branch 'master' into export_include_dir
Merge pull request #7 from nschloe/export_include_dir

fix relative path in project export files
include subpackage exports in superpackage export files
Fixing usage of NativeRepositoriesList.cmake

When a TriBITS repo's PackagesList.cmake file uses the macro
TRIBITS_REPOSITORY_DEFINE_PACKAGES() and the repo was defined in the
NativeRepositoriesList.cmake file, the configure would fail because of an
error in logic that would not propertly set the REPOSITORY_NAME variable
before reading in the repo's PackagesList.cmake and TPLsList.cmake files.
This logic has now been fixed.

Here I also added an auotmated test for the usage of the
NativeRepositoriesList.cmake file.  I put in a hook to allow this file to be
specified using ${PROJECT_NAME}_NATIVE_REPO_FILE_OVERRRIDE for unit testing
purposes.  This variable is undocumented on purpose.  I don't want users to
know about it or use it.

Really I want NativeRepositoriesList.cmake to go away and for projects to use
ExtraRepositoriesList.cmake but first I need to implement support for
pre-extra repositories.
Updating documentation on snapshot-dir.sh
Merge remote branch 'github/master'
Regenerated develpers guide output.
Adding date and version fields to these documents

Really we should also show git repo SHA1 for development versions to be
precise.
whitespace changes (avoid superfluous newline in export)
include configuration of dependent packages in export files
Merge branch 'master' into untangle_export_files

Conflicts:
	package_arch/TribitsWriteClientExportFiles.cmake