[MNG-5889] .mvn directory should be picked when using --file

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.3, 3.3.9
• Fix Version/s: 3.5.0-alpha-1, 3.5.0
• Component/s: Bootstrap & Build
• Assignee: Tibor Digana
• Reporter: Daniel Spilker
• Created: 15/Sep/15 09:02
• Updated: 28/Mar/20 15:00
• Resolved: 14/Feb/17 07:18

Description

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.

Issue Links

• causes: MNG-6385 Windows mvn.cmd fail with incorrect command syntax.
• is related to: MNG-5858 mvn script fails to locate .mvn in current directory
• is related to: MNG-6198 mvn script fails to locate .mvn directory when pom location specified with -f
• is related to: MNG-6223 mvn -f outputs invalid error when specifying POM directory
• relates to: MNG-6256 Maven script can break if "-f" path contains special characters
• relates to: MNG-5767 project-specific default jvm options and command line parameters
• relates to: MNG-5771 improved user-configurable core extensions mechanism
• links to: GitHub Pull Request #8
• links to: GitHub Pull Request #33
• links to: GitHub Pull Request #38
• links to: GitHub Pull Request #59
• links to: GitHub Pull Request #74
• links to: GitHub Pull Request #93
• links to: GitHub Pull Request #94
• links to: GitHub Pull Request #436
• mentioned in: Page Loading...