You can try using the executor plugin to specify dependencies that are no longer allowed.
The plugin has goals to either apply the rules (thereby failing to complete the assembly) or print a violation report.
Update
I am using the Sonar dependency report to look for cross-use of legacy libraries. I know that you also use Sonar, but just in case, here is an example:
(This information comes from the Maven POM of each project analyzed by Sonar.)
I think what you are really looking for does not currently exist ... A plugin that works like a standard Maven plugin but is configured and causes a violation in Sonar!
Why don't you post this as an idea for the Sonar JIRA?
source share