You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2018/01/06 22:08:00 UTC

[jira] [Commented] (MNG-6310) settings.xml allow proxy activation by expression

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

Karl Heinz Marbaise commented on MNG-6310:
------------------------------------------

Are you using a repository manager ? Why do you need to many activations ? Can you give a more detailed example of that?

> 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
(v6.4.14#64029)