[Completes #99933632]

This commit adds a test to prove that escaped chars are handled correctly in the environment variable values of `java_opts`.

The change adds a framework for the Safenet Luna Security Provider.
This  framework is triggered by a service with the name 'luna' in it.
It depends on that service having the HSM host, host-certificate,
client, and client-certificate.  In also expects users to provide a
repository with the Luna Client binaries in it.

[#96530962][#99962452]

[Completes #99962452]

This commit adds support for version 2.0.0 of the Java Buildpack Memory
Calculator. This includes specifying initial memory values which are
set to 100% by default in the JRE configuration files in order to
preserve existing behaviour.

[#99686520][#99679412]

This commit adds the ability to configure the number of threads the memory calculator should use when calculating the stack to allocate per thread. The default behaviour of the Java Buildpack is unchanged.

[#91088912]

Add tags information to the memory calculator documentation.

[#101134594]

Update the New Relic configuration file to the latest version.

[#101135042]

The download cache tests can fail if certain environment variables
exist on the users machine. This commit makes those tests more tolerant
of this.

[#101130824]

This change updates the Tomcat container to allow a user to configure
the context path that an application is exposed at.  Previously, the
application was always exposed at the root ('/') but this didn't work
for many applications that had hard-coded context-path assumptions. In
addition, changes to the Cloud Foundry router mean that applications
can now be routed via both a host and a context path.

[#101289516]

[Completes #101289516]

Update the no container found message to provide a more descriptive explanation and point users to further information.

[#101396370]

Previously the documentation for the JREs mentioned how to use the
resources directory to copy artifacts, but did not have any explicit
examples of where doing this might be useful.  This change updates
that documentation to provide examples of configuring JCE Unlimited
Strength and custom SSL certificates.

[cloudfoundry#216]

Adds a config file for Java Main applications to allow it to be configured by environment variables without forking the buildpack.

[#101680106]

This commit updates the appearense of the AppDynamics name where possible to more closely match their branding but without causing a breaking change to the buildpacks backwards compatibility.

[#102165010]

Aditional work to update the appearense of the AppDynamics name where possible to more closely match their branding but without causing a breaking change to the buildpacks backwards compatibility.

The buidpack will match services with both `app-dynamics` and `appdynamics` as service names/tags etc...

[#102165010]

Documentation change

[#102165010]

Documentation change

[#102165010]

This change removes CentOS and Lucid support from the buildpack.

[#101134432]

[#101134432]

This commit sets the `default_application_name` and `default_tier_name` to empty properties in the AppDynamics config file. This mean they can be easily set by an environment variable. If they are left empty and no value is given by the credentials payload of the bound AppDynamics service, then `application_name` already uses to the application name set by Cloud Foundry but the `tier_name` will now also use the application name set by Cloud Foundry for its value.

[#102469346]

This commit changes the ordering of the frameworks so that Java Opts from either the environment or the Java Opts config file will be specified after any Java Opts added by other frameworks in the application start command.

[#102143072]

This commit makes a number of changes which are required for
compatibility with Spring Insight on PCF 1.5.x.

Close cloudfoundry#222
[#102664842]

Changed name from new relic to appdynamics

Update AppDynamics config file comments

This commit corrects a typo in the AppDynamics configuration file where the wrong product name is used.

Document local_policy.jar location for 'server jre'

See: cloudfoundry#196

[Completes #109651014]

This change loosens the Luna client version from 5.3.+ to 5.+.

This change updates the Luna Security Provider framework to allow
users to enable the cklog wrapper for the Luna libraries.  Logging is
disabled by default and required Luna client 5.4.2 Alpha 2 or later.

Cleaning up ordering and format.

This change updates some of the test code to fix build breakages from the
previous commit.

This reverts commit bc41343.

Another attempt at fixing broken test from previous commit

Previously, the Java Buildpack logfile was written to the file system under
all circumstances.  This change updates the LoggerFactory to only create the
file if it explicitly configured to do so.

Previously the Luna Security Provider configuration specified HA requirements,
but did not describe the reconnection configuration.  This change adds
additional parameters that describe the reconnection behavior.

[#101905646]

This commit adds missing GemFire dependencies on Log4j.

Functionality now provided natively by buildpack

This reverts commit fd8b88c.