You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Maarten Mulders (Jira)" <ji...@apache.org> on 2019/08/28 17:38:00 UTC

[jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor

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

Maarten Mulders commented on MDEP-204:
--------------------------------------

I wouldn't mind to take a look at this and see if I can do something about it. However, I've already spent a few hours trying to debug where this is actually failing, and I can't really find where I should start. So any pointers where the problem might reside are more than welcome...

> go-offline fails to resolve artifact available in maven reactor
> ---------------------------------------------------------------
>
>                 Key: MDEP-204
>                 URL: https://issues.apache.org/jira/browse/MDEP-204
>             Project: Maven Dependency Plugin
>          Issue Type: Bug
>          Components: go-offline
>    Affects Versions: 2.0, 2.1
>         Environment: maven 2.1.0
>            Reporter: Stevo Slavic
>            Priority: Major
>         Attachments: mvn-dependency-go-offline-failing-example.zip
>
>
> Attached is example project, for which IMO dependency:go-offline should be able to resolve all dependencies as they are only intermodule dependencies within same multimodule project which haven't been installed yet but are available in maven reactor so can be considered as resolvable in offline mode - instead dependency:go-offline fails to resolve these dependencies.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)