[
https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032155#comment-15032155
]
Bill Burcham commented on MDEP-204:
-----------------------------------
An important use-case that didn't exist when this ticket was created is Docker.
A Dockerized project typically has a Dockerfile at the root of the project. The
Dockerfile contains instructions for building an image. In the Dockerfile, it
is useful to separate two kinds of processing:
1. downloading external dependencies
2. compiling (local) sources
This is the pattern for Dockerfiles in Python, Ruby, Node/JavaScript and
others. The value of structuring the Dockerfile this way is that after building
an initial image, subsequent source code changes do not incur the work in (1).
This shortens the edit-compile-run loop.
It might seem that mvn dependency:go-offline is ideally suited to (1) except
for the fact that it fails when a local project (A) depends on another local
project (B) if B has not yet been compiled and installed. But B cannot be
installed until after step (2).
Indeed, what is the point of go-offline, if it only (in general) succeeds after
install? If mvn install succeeds, all external dependencies will have been
cached locally, obviating the need to run mvn dependency:go-offline at all.
Right?
> 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
> 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
(v6.3.4#6332)
