maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hauke Jäger (JIRA) <j...@apache.org>
Subject [jira] [Commented] (MDEP-204) go-offline fails to resolve artifact available in maven reactor
Date Fri, 23 Nov 2018 10:00:01 GMT

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

Hauke Jäger commented on MDEP-204:
----------------------------------

I just stumbled on this issue which is still present in 3.6.0 and I honestly have to say i
can't believe this is still open after almost 10 years of time to fix it.

We are living in the times of Docker multi stage builds but Maven makes it very hard to being
used there.

I will have to go for Gradle...

> 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
(v7.6.3#76005)

Mime
View raw message