You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Peter Cummuskey (JIRA)" <ji...@apache.org> on 2016/07/22 00:14:20 UTC
[jira] [Commented] (MNG-5698) Declare proxies and mirrors in
profiles
[ https://issues.apache.org/jira/browse/MNG-5698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388659#comment-15388659 ]
Peter Cummuskey commented on MNG-5698:
--------------------------------------
If sorted, the connection won't be a problem, but the mirror still will be. I have the same issue. While at work, need to use the local mirror, but when I'm home, I need to resolve using all the repos. If you could put the mirror configuration in a profile, it'd make switching that a lot easier.
> Declare proxies and mirrors in profiles
> ---------------------------------------
>
> Key: MNG-5698
> URL: https://issues.apache.org/jira/browse/MNG-5698
> Project: Maven
> Issue Type: Improvement
> Components: Settings
> Environment: All
> Reporter: Edwin Wiles
>
> There appear to be 140 issues regarding proxy configuration. None of them appear to have been adequately dealt with.
> There should be a solution, internal to Maven, preferably in the settings.xml file, that allows the user to either automatically, or at worst with a -P profile argument, to switch between proxies and mirrors.
> It seems the easiest way to achieve this is to allow proxies and mirrors into profiles, the same as properties and repositories are now.
> USE CASE: I am presently dealing with an environment where company A has a mirror, proxy, and VPN access; company B has a mirror, proxy, and VPN access; and the user may be working from either company's office, either company's VPN, or from home without using either company's resources.
> Just making proxies and mirrors acceptable in profiles would go a VERY long way to solving this problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)