[jira] [Commented] (MNG-5889) .mvn directory should be picked when using --file

["Jason Young (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16726939#comment-16726939 ] 

Jason Young commented on MNG-5889:
----------------------------------

[~stephenc] Are you saying this issue is _not_ fixed in 3.5.0?

I'm seeing this issue in maven 3.6.0 similarly to how it is described in the OP. Specifically, I define the `revision` property in `root/.mvn/maven.config` but see e.g. `'dependencies.dependency.version' for com.blah:blah:jar must be a valid version but is '${revision}'` only when building from another directory via the `--file=path/to/root/pom.xml` arg.

> .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)