[
https://jira.codehaus.org/browse/MDEP-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=360575#comment-360575
]
Robert Scholte commented on MDEP-476:
-------------------------------------
If bytecode analysis is not enough, we could add a source scan with QDox. That
will find those annotations and based on their type the plugin can discover if
dependencies are really required or not.
> add the ability to ignore dependencies in the analyze-* goals
> -------------------------------------------------------------
>
> Key: MDEP-476
> URL: https://jira.codehaus.org/browse/MDEP-476
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: analyze
> Affects Versions: 2.9
> Reporter: Henning Schmiedehausen
>
> The dependency plugin is an essential tool to keep any build sane and from
> going off the rails with stale and bad dependencies. However, there are the
> few very odd corner cases where a dependency must be on the class path to
> ensure compilation but it is not detectable from byte code.
> The most prominent example for this are the
> com.google.code.findbugs:annotations and com.google.code.findbugs:jsr305
> jars, which only contain annotations but very often lead to unresolvable
> compilation problems with both jars present on the classpath.
> The analyze goals should have facilities to
> - list dependencies that should be ignored if they are declared but unused
> - list dependencies that should be ignored if they are undeclared but used
> - list dependencies that should be ignored in either case.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
