[
https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16727058#comment-16727058
]
Robert Patrick edited comment on MNG-5889 at 12/21/18 9:06 PM:
---------------------------------------------------------------
I am confused as to what problem you are trying to address. Clearly, MNG-5889
is resolved because mvn is able to find the .mvn directory when using the
--file arg. Perhaps you should open a separate defect with the details of your
problem (make sure to tag me since I don't actively monitor Maven defects).
was (Author: rhpatrick00):
I am confused as to what problem you are trying to address. Clearly, MNG-5889
is resolved because mvn is able to find the .mvn directory when using the
--file arg. Perhaps you should open a separate defect with the details of your
problem (make sure to take me since I don't actively monitor Maven defects).
> .mvn directory should be picked when using --file
> -------------------------------------------------
>
> Key: MNG-5889
> URL: https://issues.apache.org/jira/browse/MNG-5889
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build
> Affects Versions: 3.3.3, 3.3.9
> Reporter: Daniel Spilker
> Assignee: Tibor Digana
> Priority: Major
> Fix For: 3.5.0-alpha-1, 3.5.0
>
>
> The {{.mvn}} directory is not picked up when using the {{--file}} switch to
> build a project from outside of the multi-module root.
> Example:
> * the module root is {{/foo/bar}}
> * {{.mvn}} is located at {{/foo/bar/.mvn}}
> * current directory is {{/foo}}
> * Maven is invoked with {{mvn --file bar/module/pom.xml}}
> I would expect the {{.mvn}} directory detection to start at the directory of
> the POM selected by {{--file}} and then go through the parent directories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
