Enclose the fortran IT in a profile

We activate this integration by default only if /usr/bin/gfortran
is found.

This should help BuildHive run the integration tests.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Enclose the toolchain IT in a profile

We activate this integration by default only if
/home/gene099/.m2/toolchains.xml is present.

This should help BuildHive run the integration tests.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Allow specify whether to run the ITs in debug mode from the
command-line

Passing the '-Dinvoker.debug=true' command-line argument will make
sure that target/it/*/build.log will contain detailed information.

This should help us debug the remaining integration test issue with
BuildHive.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Merge branch 'run-its'

Actually, I could not resolve the BuildHive issues before merging the
branch as I hoped because BuildHive consistently builds master instead
of the branch to merge.

Oh well.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Add ability to specify the path of the desired tool

By specifying `<toolPath>` in any of the configuration sections, you can point to a compiler/linker that is not in the standard (on your path) location.
Merge branch 'config-toolPath'

# By Johannes Schindelin (3) and Nathan Toone (1)
# Via Johannes Schindelin (1) and Nathan Toone (1)
* config-toolPath:
  Add ability to specify the path of the desired tool
  Allow specify whether to run the ITs in debug mode from the command-line
  Enclose the toolchain IT in a profile
  Enclose the fortran IT in a profile