rmannibucau commented on PR #1061: URL: https://github.com/apache/maven/pull/1061#issuecomment-1489011010
> well the parent-child relation, and I often build setups where there are not really parent/child as much as the `.mvn` thing actually, we are used to get it in the root dir but with fake parents (submodules for ex) it can be in the wrong dir so both strategies are as bad but relying on a recent addition and something not required by the project sounds very fragile upfront. The parent child relationship is pretty straight forward: resolve all the graph while child is linked to a parent and relativepath != null and parent is not resolved from .m2/remote. Then take the higher folder. It is as fragile as the .mvn but always works. It is fine for me to use the .mvn as a "stop bubbling" marker if present but if none is found parent/child relationship should be used IMHO. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
