Mergeback 1.4.x

Add an optional $aliases parameter to tomcat::config::server::host
to allow the management of Alias entries within the Host entry.
If the parameter is omitted, any existing Alias entries within the Host
XML element are left unaltered.  Otherwise, the set of Alias entries
within the Host entry are set to match the content of the $aliases array.
(An empty array is supported, which allows any existing Alias entries to be
removed.)

MODULES-2984 - Add support for host aliases

(FM-4049) update to modulesync_configs

Allow puppetlabs-concat 2.x

This example should say absent

The intent is that CATALINA_BASE is separate from CATALINA_HOME

with this request CATALINA_HOME is where the apache-tomcat source is
extracted to and CATALINA_BASE is where it is configured, where webapps
are to be placed and where instances files (log, temp/work files) will
be created

It also includes

- properties for catalina.properties (this is copied from CATALINA_HOME and others added as tomcat needs some of the settings from it)
- jsvc-init - a init file for jsvc
- support setenv adding parts to a common variable
- (CATALINA_OPTS often wants many things added from different sources)
- global naming resource - (I use it for database connections)
- resourceLink in context.xml

Conflicts:
	manifests/config/context/resourcelink.pp

A lot of work was put in by Bryan Belanger <bbelanger@azcender.com> and
Neil Prockter <prockter@lse.ac.uk> to enable the tomcat module to use an
init script when installed from source, work with multiple instances
installed in separate catalina_home directories, and fill gaps in the
available resources.

This cleans up the three pull requests mentioned above and updates tests
and docs.

As of yet no acceptance tests have been written.

Clean up PR #76, #108, #109

This moves all copyright statements to the NOTICE file in accordance with the ASFs guidelines on applying the Apache-2.0 license.

(FM-4046) Update to current msync configs [006831f]

Update metadata to note Debian 8 support

Tomcat is traditionally installed into catalina_home, and multiple
instances can be created by using a custom catalina_base per instance.
The previous iteration of this was buggy, so this commit implements a
new defined resource tomcat::install which is used for declaring each
install of the software into a catalina_home, and then tomcat::instance
can deploy an instance from catalina_home to catalina_base and declare a
tomcat::service to go along with it.

The base class is used to set a few defaults to be used by all
instances.

If the old behavior is to be used, this is still possible.

Fix home/base installation

Older concats need order to be a string, not an integer.

Fix for older concats

Finish the install before creating instances

Remove function call from collector

Update for concat version install in spec helper

The documentation needed to be updated for the new define
tomcat::install and the documentation and usage around tomcat::instance
needed to be updated. The tests test the examples used in the readme.

The bugfixes:
- Fix logic for setting tomcat::instance::manage_service
- Reduce dependencies in multi-instance cases.

Update documentation and fix bugs

Forgot to update the spec with the other example

This also removes a unnecessary flatten() call. All the arguments are
strings or undef.

(maint) fix t::c::s::tomcat_users under strict variables

Status function does not return correct values, thus preventing Puppet reloading the service when needed.

fixes for jsvc-init script template

(maint) update tomcat v8 test URLs

(maint) Update to 7.0.69