[
https://issues.apache.org/jira/browse/MDEP-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768006#comment-17768006
]
Elliotte Rusty Harold commented on MDEP-885:
--------------------------------------------
I don't see a compelling use case here. You're doing something quite unusual
and outside the usual approach for Maven builds. Maven deliberately is very
opinionated about how builds are set up. And the maven-dependency-analyzer is a
completely optional part of the build process you can simply turn off or not
use with no major affect. What the analyzer is telling you is that those
dependencies are unused, which is true. If you have an idiosyncratic setup that
adds unused dependencies to a pom, that's fine. Just don't use the dependency
analyzer.
> Introduce artifactSets in analyze
> ---------------------------------
>
> Key: MDEP-885
> URL: https://issues.apache.org/jira/browse/MDEP-885
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: analyze-only
> Affects Versions: 3.6.0
> Reporter: Delany
> Assignee: Elliotte Rusty Harold
> Priority: Major
>
> As in MDEP-210, in my project all third-party artifacts, including their
> transitives, must be specified as direct dependencies. What happens is that
> these transitives get flagged as unused. I want the rule to consider only
> dependencies with a groupId identifying the artifacts I produce.
> None of the current options allow this. Please add include/exclude parameters
> so I can filter by Maven coordinates.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
