[
https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15560252#comment-15560252
]
ASF GitHub Bot commented on MNG-5889:
-------------------------------------
Github user rpatrick00 commented on the issue:
https://github.com/apache/maven/pull/94
OK, I found and resolved the problem with the --file arg but am not seeing
the other problem you describe (see output below). Maybe my fix for the --file
arg resolved that one too?
Here is a stupid little test project that I am using:
[maven-test.zip](https://github.com/apache/maven/files/518411/maven-test.zip)
In the root directory of the project, there is a git.diff file that shows
the changes I made to the pull request code. I am happy to resubmit the pull
request with this change but would prefer to verify that it fixes the issues in
your Windows environment first.
If you run with JDK 8, you will see the warning about ignoring
MaxPermSize=128m, which is set in jvm.config:
D:\temp>mvn --file maven-test\pom.xml verify
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=128m; support was removed in 8.0
[INFO] Scanning for projects...
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building maven-config-test 1.0-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- echo-maven-plugin:0.3.0:echo (default) @ maven-config-test ---
[INFO]
[INFO]
[INFO]
[INFO]
[INFO] myproperty = from.maven.config
[INFO]
[INFO]
[INFO]
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 0.587 s
[INFO] Finished at: 2016-10-09T11:20:56-05:00
[INFO] Final Memory: 17M/491M
[INFO]
------------------------------------------------------------------------
> .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
> Reporter: Daniel Spilker
> Assignee: Tibor Digana
>
> 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
(v6.3.4#6332)
