maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Patrick (JIRA)" <>
Subject [jira] [Commented] (MNG-6083) Maven 3.3.9 breaks release:perform by not including maven.config
Date Sun, 04 Sep 2016 17:31:21 GMT


Robert Patrick commented on MNG-6083:

In playing with the paths toolchain, I see how I can specify a location for my shell scripts
with it (this eliminates one of about a dozen variables I need for my system-test.  However,
I cannot figure out how to reference a variable defined in a toolset to pass as an argument
to my executable.  I tried the normal ${xxx} but that doesn't work.  Without this, it seems
that the only option is a custom toolchain *and* a custom plugin to process it (e.g., a plugin
that reads the toolchain and adds properties to the build so that they can referenced in the
pom).  While I am not afraid of writing plugins, I am concerned that I am missing something

For example, how do I make this work when the xxxv1-home is defined in the toolchain?


> Maven 3.3.9 breaks release:perform by not including maven.config
> ----------------------------------------------------------------
>                 Key: MNG-6083
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 3.3.9
>            Reporter: Robert Patrick
>            Priority: Blocker
> 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

This message was sent by Atlassian JIRA

View raw message