[jira] [Commented] (MDEP-743) go-offline doesn't resolve dependencies from non-central repos

["Piotr Zygielo (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MDEP-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318932#comment-17318932 ] 

Piotr Zygielo commented on MDEP-743:
------------------------------------

I suppose it is fixed by MDEP-680, which, sadly, is not released yet.

[~magneticflux-] You can try to use [https://jitpack.io/#pzygielo/maven-dependency-plugin/3.1.2-pz-1] to verify that fix for MDEP-680 helps in your case.

> go-offline doesn't resolve dependencies from non-central repos
> --------------------------------------------------------------
>
>                 Key: MDEP-743
>                 URL: https://issues.apache.org/jira/browse/MDEP-743
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: go-offline
>    Affects Versions: 3.1.2
>         Environment: Windows 10 Powershell; WSL 2 Debian
>            Reporter: Mitchell Skaggs
>            Priority: Major
>
> To reproduce, create a Maven project with a dependency that is not in Maven Central. The one I used is located at [https://jitpack.io/#bhlangonijr/chesslib]. Add Jitpack as a repository like normal, and then run `go-offline`. The task fails because it can't resolve the artifact in Maven Central.
>  
> I did some debugging and found that the task doesn't have the Jitpack repository in the list to check, even though the artifact is resolved normally for compilation and running.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)