[
https://issues.apache.org/jira/browse/MNG-5889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15666360#comment-15666360
]
ASF GitHub Bot commented on MNG-5889:
-------------------------------------
GitHub user neykov opened a pull request:
https://github.com/apache/brooklyn-client/pull/33
Set default JVM memory settings for the build
* Will be picked up when building a sub-module
* Doesn't work with `--file` option
([MNG-5889](https://issues.apache.org/jira/browse/MNG-5889))
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/neykov/brooklyn-client maven-opts
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-client/pull/33.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #33
----
commit 8cf2f37dc8a8582d50c2f3bac98e7512a2be6716
Author: Svetoslav Neykov <svetoslav.ney...@cloudsoftcorp.com>
Date: 2016-11-15T07:18:10Z
Set default JVM memory settings for the build
----
> .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
> Fix For: 3.4.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
(v6.3.4#6332)
