maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MNG-5889) .mvn directory should be picked when using --file
Date Sun, 13 Nov 2016 18:23:58 GMT


ASF GitHub Bot commented on MNG-5889:

Github user hboutemy commented on the issue:
    let's help: I dug into core-its, to find what existing IT to extend, since .mvn feature
should have an IT already
    => found mng-5771-core-extensions IT, which already tests 3 conditions: I think it's
the right place to add one more
    here are the pointers:
    - the IT source:
    - associated test projects:
    I suppose writing the IT will simply require to copy testCoreExtension() method and not
setting basedir on the Verifier, but add the new option
    here is core-its intro:
    do you want to try? Or I do it (now that I had a look and found existing IT, seems easy)

> .mvn directory should be picked when using --file
> -------------------------------------------------
>                 Key: MNG-5889
>                 URL:
>             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

View raw message