[
https://issues.apache.org/jira/browse/MNG-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15952797#comment-15952797
]
Hervé Boutemy commented on MNG-6198:
------------------------------------
ok, found why th eexisting IT did not fail: if {{.mvn}} directory is in the
same directory than {{-f pom.xml}}, it is correctly detected (by accident: if
{{.mvn}} is not found, default value is the directory from {{pom.xml}})
the failure happens if {{.mvn}} has to be found in a parent directory, since as
you pointed out, the search does not start from {{pom.xml}} directory but from
current dir...
I'll improve MNG-5889 IT
> mvn script fails to locate .mvn directory when pom location specified with -f
> -----------------------------------------------------------------------------
>
> Key: MNG-6198
> URL: https://issues.apache.org/jira/browse/MNG-6198
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.5.0-alpha-1, 3.5.0-beta-1
> Reporter: Stephen Connolly
> Assignee: Stephen Connolly
> Fix For: 3.5.0
>
>
> Steps to reproduce
> {code}
> $ mkdir apache
> $ cd apache
> $ git clone https://git-wip-us.apache.org/repos/asf/maven.git
> $ mkdir .mvn
> $ cd .mvn
> $ echo -DskipTests > maven.config
> $ cd ../maven
> $ mvn install # notice tests are skipped
> $ cd ../..
> $ mvn install -f apache/maven/pom.xml # notice tests not skipped (bug)
> $ cd apache
> $ mvn install -f maven/pom.xml # notice tests are skipped (accident)
> {code}
> The issue is that we do not search for the .mvn folder from the directory
> specified from {{-f}} rather from the current working directory
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
