Add an option to ignore unresolvable signatures

[GoogleCodeExporter]

As explained in issue #10, I would like to propose a new feature for the Maven 
plugin, namely an option to ignore unresolvable signatures, i.e. signatures 
referring to classes that are not found in the dependencies of the Maven 
project.

The use case is to enforce a forbidden-api check for a custom library (not APIs 
from the JRE) on an entire multi-module Maven project (including modules that 
are added later) where some of the modules don't have a dependency on that 
library. If there was an option to ignore unresolvable signatures, then this 
use case can simply be implemented by configuring the execution of the 
forbidden-api in the parent POM. With the current Maven plugin this doesn't 
work because it would fail on the modules that don't have the custom library as 
dependency. The only way would be to configure the plugin individually in each 
module that has the dependency, but this solution is not practical and it's not 
possible to enforce the check on modules that are added later.

Original issue reported on code.google.com by [email protected] on 13 Oct 2013 at 2:41

Attachments:

• failOnUnresolvableSignatures.patch