[
https://issues.apache.org/jira/browse/BUILDR-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Donald updated BUILDR-476:
--------------------------------
Fix Version/s: 1.5
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
