You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Paul Benedict (JIRA)" <ji...@codehaus.org> on 2009/10/30 20:13:26 UTC
[jira] Commented: (MNG-4420) It should be possible to define your
mirrors section inside a profile
[ http://jira.codehaus.org/browse/MNG-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196699#action_196699 ]
Paul Benedict commented on MNG-4420:
------------------------------------
Do mirrors really fall under project management -- the POM? I think they are better as a "system" property in settings.xml
> It should be possible to define your mirrors section inside a profile
> ---------------------------------------------------------------------
>
> Key: MNG-4420
> URL: http://jira.codehaus.org/browse/MNG-4420
> Project: Maven 2
> Issue Type: New Feature
> Components: Profiles, Settings
> Affects Versions: 2.2.1
> Reporter: Martin Todorov
> Priority: Minor
>
> At the moment, the settings.xml is the only place you can specify a mirror at the top-level. It should be possible to have profiles in your settings.xml where you could specify different mirrors.
> Consider the following scenario:
> Your company has two repositories. The first one contains artifacts for internal development use only (sources of third-party artifacts, their javadocs, etc). The second one is used only for releases and is accessed by externals/partners. Yes, you can always create profiles and have the respective repository sections in there. However it's a lot easier to have this handled by Nexus where all these repositories have been added and just have two wildcard mirrors (according to the profile) - one for internal use and one for external.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira