[
https://issues.apache.org/jira/browse/MDEP-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215600#comment-17215600
]
Maarten Mulders commented on MDEP-725:
--------------------------------------
Oh, of course, that makes perfect sense. Indeed, using {{excludedArtifactIds}}
should not be needed to exclude dependencies that are available in the Reactor.
Maybe the exclusion is not working at all, let's say for dependencies outside
the Reactor. If that is the case, I'd say that is a bug indeed. It is not what
this ticket says explicitly, but the [answer by the OP on
StackOverflow|https://stackoverflow.com/a/64241726/1523342] suggests that is
the case.
> excludeGroupIds, excludeArtifactIds not working for go-offline goal
> -------------------------------------------------------------------
>
> Key: MDEP-725
> URL: https://issues.apache.org/jira/browse/MDEP-725
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: go-offline
> Affects Versions: 3.1.1
> Reporter: Mahmoud Anouti
> Priority: Major
>
> When applying -DexcludeGroupIds or -DexcludeArtifactIds to exclude project
> dependencies from resolution, they still get resolved and downloaded by
> `go-offline`:
> mvn dependency:go-offline -DexcludeArtifactIds=example-core
>
> [INFO] — maven-dependency-plugin:3.1.1:go-offline (default-cli) @
> rest-example —
> ...
> [INFO] Resolved: example-core-1.0.jar
> Also reported in
> [https://stackoverflow.com/questions/51113813/mvn-dependencygo-offline-how-do-you-set-params-on-the-command-line-or-at-all]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
