New Relic to give priority to java_opts

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]

Author: Christopher Frost

config/components.yml

@@ -31,17 +31,20 @@ jres:
   - "JavaBuildpack::Jre::OpenJdkJRE"
 # - "JavaBuildpack::Jre::OracleJRE"
 
+# Frameworks are processed in order. Any Java Opts added by the JavaOpts framework will be specified in the start
+# command after any Java Opts added by previous frameworks.
+
 frameworks:
   - "JavaBuildpack::Framework::AppDynamicsAgent"
 # - "JavaBuildpack::Framework::IntroscopeAgent"
 # - "JavaBuildpack::Framework::DynaTraceAgent"
-  - "JavaBuildpack::Framework::JavaOpts"
   - "JavaBuildpack::Framework::JrebelAgent"
-#  - "JavaBuildpack::Framework::LunaSecurityProvider"
+# - "JavaBuildpack::Framework::LunaSecurityProvider"
   - "JavaBuildpack::Framework::MariaDbJDBC"
   - "JavaBuildpack::Framework::NewRelicAgent"
   - "JavaBuildpack::Framework::PlayFrameworkAutoReconfiguration"
   - "JavaBuildpack::Framework::PlayFrameworkJPAPlugin"
   - "JavaBuildpack::Framework::PostgresqlJDBC"
   - "JavaBuildpack::Framework::SpringAutoReconfiguration"
   - "JavaBuildpack::Framework::SpringInsight"
+  - "JavaBuildpack::Framework::JavaOpts"

docs/framework-java_opts.md

@@ -27,6 +27,8 @@ The framework can be configured by creating or modifying the [`config/java_opts.
 
 Any `JAVA_OPTS` from either the config file or environment variables that configure memory options will cause deployment to fail as they're not allowed. Memory options are configured by the buildpack and may not be modified.
 
+Any `JAVA_OPTS` from either the config file or environment variables will be specified in the start command after any Java Opts added by other frameworks.
+
 ## Example
 ```yaml
 # JAVA_OPTS configuration