[
https://issues.apache.org/jira/browse/MNG-6762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522852#comment-17522852
]
Łukasz Dywicki commented on MNG-6762:
-------------------------------------
Understand, so to minimize impact this issue makes on me I started looking for
workaround. One part of issue is handling of relative settings location, but
other was really artifact resolution. Even if I had all artifacts cached in
local and forced offline mode (-o -nsu), maven did insist on re-resolving them.
I have mirrors which masks remote repos and reactor could not work without
them, even in offline mode.
For me solution is:
{noformat}
mvn -o -nsu -s ~/.m2/settings.xml -llr install
{noformat}
First part switch offline mode, then it reset settings to defaults, last one
disable handling of {{_remote.repositories}} file which is contributing factor
why re-resolving was made.
So with this workaround I can keep going. :)
Best, Łukasz
> Multimodule project with .mvn/settings.xml not working properly
> ---------------------------------------------------------------
>
> Key: MNG-6762
> URL: https://issues.apache.org/jira/browse/MNG-6762
> Project: Maven
> Issue Type: Improvement
> Affects Versions: 3.5.4
> Reporter: Morten Minke
> Priority: Minor
> Fix For: waiting-for-feedback, wontfix-candidate
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I have a project with the following setup:
>
> {noformat}
> - MyProject
> |- .mvn
> | |- maven.config
> | |- settings.xml
> |- MyModule1
> | |- pom.xml
> |- MyModule2
> | |- pom.xml
> |- pom.xml{noformat}
>
> The .mvn/maven.config file contains the following:
> {noformat}
> ..
> --settings .mvn/settings.xml{noformat}
> With this setup, I cannot build the modules separately because it cannot find
> the .mvn/settings.xml file in the MyModule1 directory.
>
> I looked into the code and saw that in the mvn script, the .mvn folder is
> searched for in the parent folders. If it is found, that folder is marked as
> the 'maven.multiModuleProjectDirectory'.
>
> However, as soon as the configuration is loaded, this
> multiModuleProjectDirectory is not used anymore for the interpretation of the
> --settings property, therefor maven tries to find the .mvn/settings.xml file
> inside the MyModule1 folder where it is not found.
> This results in an Exception and termination of Maven.
>
> I thought of a couple of ways this could be solved:
> * Allow for a variable substitution to work in the maven.config file and
> thus reference something like:
> {noformat}
> ..
> --settings ${baseDir}/.mvn/settings.xml{noformat}
> * When the maven.multiModuleProjectDirectory is configured and the
> --settings flag is a relative directory, than use the
> maven.multiModuleProjectDirectory as the root to obtain the settings.xml file.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
