[
https://issues.apache.org/jira/browse/MDEP-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809866#comment-17809866
]
Fabrice Bacchella commented on MDEP-904:
----------------------------------------
When doing build on CI tools, I like to separate steps that resolve
dependencies from step that builds and step that run tests, it make
understanding problems easier, as maven resolving dependencies is very verbose.
To do the same things without go-offline, I will needs something like “mvn test
-Dmaven.test.skip=true -Dmaven.main.skip=true” but that will not be enough.
So both solutions are broken, which one is the least broken ?
> Drop go-offline goal
> --------------------
>
> Key: MDEP-904
> URL: https://issues.apache.org/jira/browse/MDEP-904
> Project: Maven Dependency Plugin
> Issue Type: Task
> Components: go-offline
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0
>
>
> The simplest and trivial way to "go offline" is to quick build (using
> {{-Dtest=void}} and NOT {{-DskipTests}}!) the project with empty local
> repository and use that.
> There are two "go offline" mojos out there (ours and an independent one) and
> both suffer from issues like "annotation processor is not downloaded", etc.
> This will just become worse. But not only this: by NOT building but by
> artificially collecting artifacts needed for build and resolving them (not
> doable correctly, only "almost correctly") messes up the recorded contexts in
> the reverse dependency tree in local repository as well.
> Remember, Maven2 times are past, Maven3+ local repository is much much more
> than Maven2 local repository was, just a bunch a files...
> Related issues:
> * https://issues.apache.org/jira/browse/MRESOLVER-262
> * https://issues.apache.org/jira/browse/MNG-7619
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
