Andy Wilkinson 681a866cce Exclude Java agents from class loader created by PropertiesLauncher ... PropertiesLauncher creates a ClassLoader that is used by the Launcher to load an application’s classes. During the creation of this ClassLoader URLs from its ClassLoader. This resulted resulting in Java agents that are added to the system class loader via the -javaagent launch option being available on both the system class loader and the created class loader. Java agents are intended to always be loaded by the system class loader. Making them available on another class loader breaks this model. This is the same problem that was in ExecutableArchiveLauncher and that was fixed in ee08667e (see gh-863). This commit updates PropertiesLauncher so that it skips the URLs of any Java agents (found by examining the JVM’s input arguments) when copying URLs over to the new ClassLoader, thereby ensuring that Java agents are only ever loaded by the system class loader. Closes gh-4911		2016-01-14 17:05:08 +00:00
..
spring-boot-configuration-processor	Fix SNAPSHOT version	2015-12-17 14:15:14 +01:00
spring-boot-dependency-tools	Fix SNAPSHOT version	2015-12-17 14:15:14 +01:00
spring-boot-gradle-plugin	Fix SNAPSHOT version	2015-12-17 14:15:14 +01:00
spring-boot-loader	Exclude Java agents from class loader created by PropertiesLauncher	2016-01-14 17:05:08 +00:00
spring-boot-loader-tools	Fix SNAPSHOT version	2015-12-17 14:15:14 +01:00
spring-boot-maven-plugin	Fix SNAPSHOT version	2015-12-17 14:15:14 +01:00
pom.xml	Fix SNAPSHOT version	2015-12-17 14:15:14 +01:00