It would be good to have more meaningful logging for class resolution. From cplummer email.

The log mostly has [classresolve] entries. Often there are many, sometimes a hundred or more, for the same file, even for the same line number in the file:

 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 [0.179s][info ][classresolve] java.lang.Integer$IntegerCache java.lang.Integer Integer.java:1049
 
This logging was converted to 'info' level but this is not terribly informative.

I made this a 'bug' because this output overwhelms meaningful output in log=all (and chris is seeing GCBasher log files as big as 2.5g). This output is excessive.