[
https://issues.apache.org/jira/browse/MNG-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Randall updated MNG-6310:
-------------------------------
Description:
Currently it appears that {{settings.xml}} proxies can only be activated via a
boolean {{active}} element, which does not appear to be evaluated, so you
cannot use a property (e.g. set by a profile), nor a system or environment
property.
This comes up a lot on discussions from developers trying to automate whether
Maven's proxies are enabled or not, based on a system or environment property
etc.
Possible solutions:
* Change the model for (generate) {{Proxy.active}} allowing an expression to
then be evaluated.
* Copy {{profiles}} approach and add an {{<activation>}} element, but this
requires a settings schema rev.
was:
Currently it appears that {{settings.xml}} proxies can only be activated via a
boolean {{active}} element, which does not appear to be evaluated, so you
cannot use a property (e.g. set by a profile), nor a system or environment
property.
This comes up a lot on discussions from developers trying to automate whether
Maven's proxies are enabled or not, based on a system or environment property
etc.
Possible solutions:
* Change the model for (generate) {{Proxy.active}} allowing an expression to
then be evaluated.
* Copy {{profiles}} approach and add an {{<activation>>}} element, but this
requires a settings schema rev.
> settings.xml allow proxy activation by expression
> -------------------------------------------------
>
> Key: MNG-6310
> URL: https://issues.apache.org/jira/browse/MNG-6310
> Project: Maven
> Issue Type: New Feature
> Components: Bootstrap & Build
> Affects Versions: 3.5.2
> Reporter: Brett Randall
> Priority: Minor
>
> Currently it appears that {{settings.xml}} proxies can only be activated via
> a boolean {{active}} element, which does not appear to be evaluated, so you
> cannot use a property (e.g. set by a profile), nor a system or environment
> property.
> This comes up a lot on discussions from developers trying to automate whether
> Maven's proxies are enabled or not, based on a system or environment property
> etc.
> Possible solutions:
> * Change the model for (generate) {{Proxy.active}} allowing an expression to
> then be evaluated.
> * Copy {{profiles}} approach and add an {{<activation>}} element, but this
> requires a settings schema rev.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
