[
https://issues.apache.org/jira/browse/MDEP-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215576#comment-17215576
]
Maarten Mulders commented on MDEP-725:
--------------------------------------
{quote}
[~mthmulders] there's no need to exclude reactor modules anymore, right?
{quote}
If you mean, because of the recent improvements in resolving dependencies that
reside elsewhere in the reactor (such as
[MNG-4660|https://issues.apache.org/jira/browse/MNG-4660]) - then indeed, it
shouldn't be necessary to exclude them for {{go-offline}} since they are always
available. That is Mavens own dependency resolution. If I'm not mistaken, the
M-D-P uses that mechanism, so using a 3.7.0 SNAPSHOT build of Maven it might
turn out to work as expected.
> 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.2
> 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)
