[
https://issues.apache.org/jira/browse/MDEP-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809861#comment-17809861
]
Tamas Cservenak commented on MDEP-904:
--------------------------------------
[~fbacchella] Well, "same thing" I assume is "local repository is primed", at
least that is the intent of this goal, no? Why is it a problem for you? Or
could you also skip compiler maybe?
> 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)
