[
https://issues.apache.org/jira/browse/MDEP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919331#comment-16919331
]
Maarten Mulders edited comment on MDEP-204 at 8/30/19 8:56 AM:
---------------------------------------------------------------
It seems that when the project is not going to be packaged, nor going to be
compiled, the {{org.apache.maven.ReactorReader}} considers the project output
dir to be non-present.
Because of this, the {{org.apache.maven.ReactorReader}} considers the requested
artifact as not part of the Reactor. The
{{org.apache.maven.repository.internal.DefaultVersionResolver}} that invoked it
then decides to contact the remote repositories to see if they have the
artifact.
As a consequence, doing {{mvn dependency:go-offline compile}} succeeds - but
that's not really a solution :-)
was (Author: mthmulders):
It seems that when the project is not going to be packaged, nor going to be
compiled, the {{org.apache.maven.ReactorReader}} considers the project output
dir to be non-present.
Because of this, the {{org.apache.maven.ReactorReader}} considers the requested
artifact as not part of the Reactor. The
{{org.apache.maven.repository.internal.DefaultVersionResolver}} that invoked it
then decides to contact the remote repositories to see if they have the
artifact.
> 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)
