Better surface class-parse Java resolve errors to users

[jingliancui]

@jpobst @jonpryor
Something packages should be added for compiling or some classes or namespace will lost, but this packages message will give to users only use jar2xml setting.
And jar2xml will be removed in the feature.
So you should move J2X9001 to class-parse from jar2xml.

[jingliancui]

I don't know what change internal in #682 (comment) .
But maybe useful here.

[jpobst]

After a quick look, I think the root problem here is that "errors" in the class-parse Java type resolution phase do not get surfaced to the user as MSBuild errors/warnings. They only show up in the build log, and only if the verbosity is set to Detailed or Diagnostic. With the correct verbosity, the build log should show a message like:

Error while processing '[Class] com.scwang.smart.refresh.layout.SmartRefreshLayout': Type 'android.support.v4.view.NestedScrollingParent' was not found.

We should convert these to proper MSBuild warnings or some other mechanism that ensures they get displayed to the user.