maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Patrick (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (MNG-6083) Maven 3.3.9 breaks release:perform by not including maven.config
Date Fri, 02 Sep 2016 20:14:20 GMT

    [ https://issues.apache.org/jira/browse/MNG-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459480#comment-15459480
] 

Robert Patrick edited comment on MNG-6083 at 9/2/16 8:13 PM:
-------------------------------------------------------------

And how exactly do you propose that would work if the property values vary across the environments
where it needs to run (e.g., Windows vs. Linux)?  You have made it very clear that you believe
in checking the maven.config file into source control.  What you haven't made clear is how
you would handle environment-specific dependencies that the project has without the developers
stepping on each other by overwriting maven.config every time they check in.  Clearly, you
don't feel like maven.config is the solution for this.  So what is?


was (Author: rhpatrick00):
And how exactly do you propose that would work if the property values vary across the environments
where it needs to run (e.g., Windows vs. Linux)?  You have made it very clear that you believe
in checking the maven.config file into source control.  What you haven't made clear is how
you you handle environment-specific dependencies that the project has without the developers
stepping on each other by overwriting maven.config every time they check in.  Clearly, you
don't feel like maven.config is the solution for this.  So what is?

> 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: 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
distribution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message