[
https://issues.apache.org/jira/browse/MNG-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-6586:
--------------------------------
Description:
Hello,
In setting reference[1] it is written:
{quote}
|{{proxies/[proxy|https://maven.apache.org/ref/3.6.0/maven-settings/settings.html#class_proxy]*}}|{{List<Proxy>}}|*(Many)*
Configuration for different proxy profiles. Multiple proxy profiles might come
in handy for anyone working from a notebook or other mobile platform, to enable
easy switching of entire proxy configurations by simply specifying the profile
id, again either from the command line or from the defaults section below.|
{quote}
So it should be possible to enable/disable proxy based on a profile. However,
there is no instructions of how to do that.
Adding <active>${property}</active> automatically disables the entry, even if
property is set to true, I verify this using help:effective-settings. I could
not find any property that can make any difference.
I see many people have tried and failed, and based on the above documentation
it seems like either missing documentation or an actual bug.
Please allow that, as multiple setting.xml are not supported and enable/disable
proxy is required for a single CI settings.xml.
Thanks!
[1] https://maven.apache.org/ref/3.6.0/maven-settings/settings.html#settings
was:
Hello,
In setting reference[1] it is written:
"""
|{{proxies/[proxy|https://maven.apache.org/ref/3.6.0/maven-settings/settings.html#class_proxy]*}}|{{List<Proxy>}}|*(Many)*
Configuration for different proxy profiles. Multiple proxy profiles might come
in handy for anyone working from a notebook or other mobile platform, to enable
easy switching of entire proxy configurations by simply specifying the profile
id, again either from the command line or from the defaults section below.|
"""
So it should be possible to enable/disable proxy based on a profile. However,
there is no instructions of how to do that.
Adding <active>${property}</active> automatically disables the entry, even if
property is set to true, I verify this using help:effective-settings. I could
not find any property that can make any difference.
I see many people have tried and failed, and based on the above documentation
it seems like either missing documentation or an actual bug.
Please allow that, as multiple setting.xml are not supported and enable/disable
proxy is required for a single CI settings.xml.
Thanks!
[1] https://maven.apache.org/ref/3.6.0/maven-settings/settings.html#settings
> Allow proxy activation based on profile
> ---------------------------------------
>
> Key: MNG-6586
> URL: https://issues.apache.org/jira/browse/MNG-6586
> Project: Maven
> Issue Type: Bug
> Components: Documentation: General, Settings
> Affects Versions: 3.6.0
> Reporter: Alon Bar-Lev
> Priority: Major
>
> Hello,
> In setting reference[1] it is written:
> {quote}
> |{{proxies/[proxy|https://maven.apache.org/ref/3.6.0/maven-settings/settings.html#class_proxy]*}}|{{List<Proxy>}}|*(Many)*
> Configuration for different proxy profiles. Multiple proxy profiles might
> come in handy for anyone working from a notebook or other mobile platform, to
> enable easy switching of entire proxy configurations by simply specifying the
> profile id, again either from the command line or from the defaults section
> below.|
> {quote}
> So it should be possible to enable/disable proxy based on a profile. However,
> there is no instructions of how to do that.
> Adding <active>${property}</active> automatically disables the entry, even if
> property is set to true, I verify this using help:effective-settings. I could
> not find any property that can make any difference.
> I see many people have tried and failed, and based on the above documentation
> it seems like either missing documentation or an actual bug.
> Please allow that, as multiple setting.xml are not supported and
> enable/disable proxy is required for a single CI settings.xml.
> Thanks!
>
> [1] https://maven.apache.org/ref/3.6.0/maven-settings/settings.html#settings
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
