[
https://jira.codehaus.org/browse/MNG-5790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=365487#comment-365487
]
Jason van Zyl commented on MNG-5790:
------------------------------------
Oh, you're putting the property in the actual maven.config file. That's not
supported right now, and not sure it can be without looking at the scripts. The
${maven.multiModuleProjectDirectory} is passed into the Maven invocation from a
calculation performed in the scripts. The jvm.config and maven.config have no
interpolation. This is not a bug, but add a feature request and we'll see if we
can do it. It would be an easy way to provide project level settings.
> Project specific options cannot resolve paths
> ---------------------------------------------
>
> Key: MNG-5790
> URL: https://jira.codehaus.org/browse/MNG-5790
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.3.1
> Environment: java version "1.8.0_40"
> Java(TM) SE Runtime Environment (build 1.8.0_40-b25)
> Java HotSpot(TM) 64-Bit Server VM (build 25.40-b25, mixed mode)
> Reporter: Filipe Sousa
>
> I have "-s ~/.m2/settings-foo.xml" in my
> ${maven.projectBasedir}/.mvn/maven.config and maven complains about missing
> file.
> [ERROR] The specified user settings file does not exist:
> /Users/fsousa/Projects/foo/governor/~/.m2/settings-foo.xml
> I tried with "-s ${user.home}/.m2/settings-foo.xml" and this time
> [ERROR] The specified user settings file does not exist:
> /Users/fsousa/Projects/foo/governor/${user.home}/.m2/settings-foo.xml
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
