You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Benjamin Marwell (Jira)" <ji...@apache.org> on 2020/01/24 22:05:00 UTC

[jira] [Issue Comment Deleted] (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:all-tabpanel ]

Benjamin Marwell updated MDEP-204:
----------------------------------
    Comment: was deleted

(was: Any ETA for MDEP v3.1.2? Thanks :)

 

[~michael-o]

> Consider that this is a volunteer project, none of us gets paid for this.

Well yes, of course. But even issues with a patch attached sometimes are not solved. There's nothing a user could do.

 )

> 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 Slavić
>            Assignee: Robert Scholte
>            Priority: Major
>             Fix For: 3.1.2
>
>         Attachments: mvn-dependency-go-offline-failing-example.zip
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> 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.4#803005)