You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Antoine Toulme (JIRA)" <ji...@apache.org> on 2016/08/14 06:38:22 UTC
[jira] [Resolved] (BUILDR-476) Buildr doesn't respect company
repository manager
[ https://issues.apache.org/jira/browse/BUILDR-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme resolved BUILDR-476.
-----------------------------------
Resolution: Fixed
> Buildr doesn't respect company repository manager
> -------------------------------------------------
>
> Key: BUILDR-476
> URL: https://issues.apache.org/jira/browse/BUILDR-476
> Project: Buildr
> Issue Type: Bug
> Components: Dependency management
> Affects Versions: 1.4.1
> Reporter: Martijn Dashorst
> Assignee: Antoine Toulme
> Fix For: 1.5
>
>
> At our company we use artifactory as our repository manager and everybody is required to use this as the only way to download maven artifacts. However, whenever a repository is added to buildr's build script, it will query that new repository as well as the one specified in the buildr yaml file, bypassing the company policy.
> Using company repositories is a best practice for several reasons: less dependency on external servers falling down (remember the maven1 days and ibiblio?), less load on Maven's central repository, and control over what repositories are acceptable for use at a company level.
> Basically I'm asking for support of the Maven setting described at http://maven.apache.org/guides/mini/guide-mirror-settings.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)