Improve d2d problem reporting for Java (and others)

[pombredanne]

I create a map_deploy_to_develop project with these Java inputs:

• https://repo1.maven.org/maven2/org/apache/htrace/htrace-core/4.0.0-incubating/htrace-core-4.0.0-incubating-sources.jar#from
• https://repo1.maven.org/maven2/org/apache/htrace/htrace-core/4.0.0-incubating/htrace-core-4.0.0-incubating.jar#to

I would like to improve access to the issues in this d2d:

1. I would like to report the main problems as requiring review. The real issue are unmapped "to" file Resources (no directory) with any status, with this URL query tag=to&relation_map_type=none https:///project/ht2-77ac4666/resources/?tag=to&relation_map_type=none&type=file and this even if they are matched to the PurlDB

Be mindful also that unmapped, but matched code may or may not be an issue at all times.

• for a large App codebase, the matched-and-unmapped are generally OK, as these are packages included in the App at build time
• for a single package codebase, the matched-and-unmapped are problematic as these are packages included in the codebase at build time and are the sign of a problem (like in xz, or like here with htrace including many third-party in an Uberjar)

2. These paths are reported as "require-review" but they should not as they are things that were created the build? I am not

• to/META-INF/MANIFEST.MF
• to/META-INF/maven/org.apache.htrace/htrace-core/pom.properties
• to/META-INF/maven/org.apache.htrace/htrace-core/pom.xml

See also:

• https://github.com/nexB/scancode.io/issues/1148