[
https://issues.apache.org/jira/browse/MNG-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15455263#comment-15455263
]
Robert Patrick commented on MNG-6083:
-------------------------------------
Well... In our case, we need to add things like "where is the database
software installed" so that we can use the database client (e.g., sqlplus) to
create/populate the necessary database tables that we need for our integration
tests. This all works fine in Maven 3.3.3 so something that was changed in
3.3.9 changed the behavior.
If I cannot use maven.config for environment-specific details, what do you
suggest? Environment variables? System properties? I thought the whole idea
of maven.config was to remove those undocumented project dependencies and make
them part of the project. We have a maven.config-template file checked in.
The developers copy that file and edit it for their environment. I suppose we
could be more nazi-like and tell them that they all have to have everything in
their environment in the specified location but, if you have ever worked with
developers, that rubs them the wrong way... :-)
> 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)
