I have a maven project style with the following configuration for the maven compiler plugin

            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>2.3.2</version>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                    <compilerId>jdt</compilerId>
                    <showWarnings>true</showWarnings>
                </configuration>               
            </plugin>

The jenkins config scan for compiler warnings using two parsers: Eclipse Java compiler and Java compiler. None of the advanced options are enabled (see screnshot). I have a not so big project with around 20 compiler warnings.

I am running Jenkins 1.459 with the warnings plugin 3.26 and this is working fine (the graph is generated, new warnings are found, etc).

If I switch to the new configuration (and that's been a long time I want to upgrade), the job is stuck when parsing the warnings. This is exactly similar to JENKINS-10097. See the configuration of 1.459 with the latest warnings plugins.