Globally exclude all Spring JavaConfig from Clover code coverage
<p>I use Spring JavaConfig to define my Spring configuration. Since unit tests use a different Spring configuration than production code, the production configuration shows up as 100% uncovered when I use Clover code coverage with unit tests.</p>

<p>I can use the <code>@Configuration</code> annotation to identify all these classes. Alternatively, I can use the <code>@Bean</code> annotation to identify all the methods within these classes.</p>

<p>Is there a Clover <code>exclude</code> or a code context filter that I can set up to globally exclude code by using these annotations? I use the <code>maven-clover2-plugin</code> to run Clover.</p>