[jira] [Updated] (MNG-6083) Maven 3.3.9 breaks release:perform by not including maven.config

["Sylwester Lachiewicz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylwester Lachiewicz updated MNG-6083:
--------------------------------------
    Priority: Major  (was: Blocker)

> Maven 3.3.9 breaks release:perform by not including maven.config
> ----------------------------------------------------------------
>
>                 Key: MNG-6083
>                 URL: https://issues.apache.org/jira/browse/MNG-6083
>             Project: Maven
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 3.3.9
>            Reporter: Robert Patrick
>            Priority: Major
>
> Our release process runs both our build and our integration tests.  The integration tests rely on our project root directory's .mvn/maven.config file to run properly.  The maven.config file is NOT checked into the source tree because it contains environment-specific values so each developer has their own version of it on each machine on which they build.
> This has been working fine for months now but simply changing the version of Maven used from 3.3.3 to 3.3.9 causes the build to break due to not having the -Ds defined in $PROJECT_ROOT/.mvn/maven.config.
> It appears that the release:perform goal checks out the release source in another location and with Maven 3.3.9, the maven.config from the original location is not being used.  The build specifies the release-plugin version so the difference seems to be in the core Maven distribution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)