[
https://issues.apache.org/jira/browse/MNG-7074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Loïc Hermann updated MNG-7074:
------------------------------
Description:
Hi all,
maven build in CI environment often rely on environnement variables.
If those environment variables are not defined on the developper environment
the build will fail.
{{For now defaulting those environment variable can only be done by defining
one profile per variable which is really verbose.}}
{{it would be easier if we can either}}
{{add a default value where the variable is used:}}
```
{{$\{env.VARIABLE_NAME:defaultValue}}}
```
or have a section to define default values in the pom:
```
<environment>
<{{VARIABLE_NAME}}>defaultValue</{{VARIABLE_NAME}}>
<environment/>
```
I would love to work on a PR to implements one of those solution if this make
sense to you.
Regards
was:
Hi all,
Many times when using maven build specific environnement variables need to be
injected in CI environnent.
If those environment variables are not defined on the developper environment
the build will fail.
{{For now defaulting those environment variable can only be done by defining
one profile per variable which is really verbose.}}
{{it would be easier if we can either}}
{{add a default value where the variable is used:}}
```
{{$\{env.VARIABLE_NAME:defaultValue}}}
```
or have a section to define default values in the pom:
```
<environment>
<{{VARIABLE_NAME}}>defaultValue</{{VARIABLE_NAME}}>
<environment/>
```
I would love to work on a PR to implements one of those solution if this make
sense to you.
Regards
> Environment Variable defaulting
> -------------------------------
>
> Key: MNG-7074
> URL: https://issues.apache.org/jira/browse/MNG-7074
> Project: Maven
> Issue Type: New Feature
> Reporter: Loïc Hermann
> Priority: Major
>
> Hi all,
> maven build in CI environment often rely on environnement variables.
> If those environment variables are not defined on the developper environment
> the build will fail.
> {{For now defaulting those environment variable can only be done by defining
> one profile per variable which is really verbose.}}
> {{it would be easier if we can either}}
> {{add a default value where the variable is used:}}
> ```
> {{$\{env.VARIABLE_NAME:defaultValue}}}
> ```
> or have a section to define default values in the pom:
> ```
> <environment>
> <{{VARIABLE_NAME}}>defaultValue</{{VARIABLE_NAME}}>
> <environment/>
> ```
> I would love to work on a PR to implements one of those solution if this make
> sense to you.
>
> Regards
--
This message was sent by Atlassian Jira
(v8.3.4#803005)