Configuration for class loader intensive applications

[almondtools]

The current Configuration (AgentConfig) is an argument of the agent command line. This configuration is propagated to the locations where it is needed, e.g. to the static filed SnapshotManager.MANAGER.

Generating Tests for Spring Applications made obvious that modern applications use their own byte code modification and their own class loaders. Consequently there are situations where SnapshotManager.MANAGER is null. This could be avoided if each class loading of SnapshotManager also initializes MANAGER and this makes it necessary to have a convention where to load the configuration from.

So this issue could be solved by:

• Load the configuration from a ServiceLoader
• Remove the configuration from the command line arguments

[almondtools]

I decided to replace the service loader completely because of two limitations:

• service loaders are restricted to loading from META-INF/services from the class path
• service loaders are restricted to classes with default constructor

The new Agentconfig ist not limited in this way.