You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mario Jauvin (Jira)" <ji...@apache.org> on 2021/05/27 01:37:00 UTC
[jira] [Comment Edited] (MNG-7162) Problem compiling, packaging or
installing multimodule project with CI friendly
[ https://issues.apache.org/jira/browse/MNG-7162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352223#comment-17352223 ]
Mario Jauvin edited comment on MNG-7162 at 5/27/21, 1:36 AM:
-------------------------------------------------------------
How do I retry using maven from master? Is this due to [MNG-7151] Upgrade Maven Resolver to 1.7.0? What has changed in Maven resolver 1.7.0? I looked at the changed files and could not determine.
was (Author: marioja):
How do I retry using maven from master?
> Problem compiling, packaging or installing multimodule project with CI friendly
> -------------------------------------------------------------------------------
>
> Key: MNG-7162
> URL: https://issues.apache.org/jira/browse/MNG-7162
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.6.3
> Environment: Windows 10
> Reporter: Mario Jauvin
> Priority: Major
>
> When using CI friendly properties if I try to compile (or even run the verify phase) on a module that does not include all of the dependencies in the reactor build, maven will attempt to resolve the dependencies not in the reactor build and fail. If you take the branch ci-friendlies from project https://github.com/marioja/maven-ear-example and cd into module-ear and type {noformat}mvn verify{noformat} you will get this error:
> {noformat}
> [ERROR] Failed to execute goal on project module-ear: Could not resolve dependencies for project com.example:module-ear:ear:2.0.0-SNAPSHOT: Failed to collect dependencies at com.example:module-web:war:2.0.0-SNAPSHOT: Failed to read artifact descriptor for com.example:module-web:war:2.0.0-SNAPSHOT: Could not transfer artifact com.example:application:pom:${revision}.${sha1}${changelist} from/to company.repository- (http://company-maven.company.net:8081/repository/maven-public): Failed to transfer http://company-maven.company.net:8081/repository/maven-public/com/example/application/${revision}.${sha1}${changelist}/application-${revision}.${sha1}${changelist}.pom. Error code 400, Invalid repository path -> [Help 1]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)