The MavenFingerprinter MavenReporter should not run if fingerprinting the build is disabled.

—
Yesterday I attached YourKit to our Jenkins Maven-style build. I was attached to the actual Maven3 builder and discovered that 36% of our build time is spent in MavenReporters we don't use. We don't have fingerprinting turned on but the MavenFingerprinter report still runs and was particularly expensive.
—

I rebuilt the maven-plugin removing the @Extension from MavenArtifactArchiver, MavenFingerprinter and MavenMailer and improved our build time by 36%. There's no good out-of-the-box way to do this with Jenkins. I had little luck when dropping in a custom PluginStrategy to do this at runtime.