updated to hold on to the configuration statically, it appears past maven 3.1.0 they have passed a new classloader to the thread running the plugin and does not set the maven classloader as the parent so when we would attempt to read the configuration file we would not find the file due to it not being in the classpath anymore