[
https://issues.apache.org/jira/browse/MDEP-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767093#comment-17767093
]
Elliotte Rusty Harold edited comment on MDEP-885 at 9/20/23 11:34 AM:
----------------------------------------------------------------------
Why? Are you flattening your poms? I've seen this happen with flattened poms,
but I'm not sure it makes sense to do used/unused analysis in that case. Nor am
I sure that analyzing by group ID would be helpful in this case. What do you
expect to find or produce in this case? That is, what problem are you trying to
solve given a flattened pom, and how would this solve it?
was (Author: elharo):
Why? Are you flattening your poms? I've seen this happen with flattened poms,
but I'm not sure it makes sense to do used/unused analysis in that case. Nor am
I sure that analyzing by group ID would be helpful in this case. What do you
expect to find or produce in this case? That is, what problem are you trying to
solve given a flattenef pom?
> Support includes/excludes configuration in analyze v2
> -----------------------------------------------------
>
> 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)
