[
https://jira.codehaus.org/browse/MSHARED-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Holger Mense updated MSHARED-411:
---------------------------------
Attachment: fix-addShellEnvironment.patch
This patch fixes this issue. JUnit test is also included.
> maven-invoker - addShellEnvironment forgets variable settings on successive
> calls
> ---------------------------------------------------------------------------------
>
> Key: MSHARED-411
> URL: https://jira.codehaus.org/browse/MSHARED-411
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-invoker
> Affects Versions: maven-invoker-2.1.1
> Environment: maven-invoker-plugin 1.9
> Reporter: Holger Mense
> Attachments: fix-addShellEnvironment.patch
>
>
> On every call of addShellEnvironment(String, String) on
> DefaultInvocationRequest the already passed environment variables are
> deleted, because a new HashMap for storing the environment variables is
> created every time. This renders the "environmentVariables" parameter of
> maven-invoker-plugin unusable when used with more then one environment
> variable.
> This issue has already been reported 2013 on
> [maven-users|http://mail-archives.apache.org/mod_mbox/maven-users/201305.mbox/%3CCAMFVGuSrgYVbWhyo1oKb+5otX55YNLcj9+jKe4B=tunmede...@mail.gmail.com%3E]
> but no JIRA has been created so this got lost.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
