You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Martijn Dashorst (JIRA)" <ji...@apache.org> on 2010/07/13 11:05:49 UTC
[jira] Created: (BUILDR-476) Buildr doesn't respect company
repository manager
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
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-476) Buildr doesn't respect company
repository manager
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888506#action_12888506 ]
Antoine Toulme commented on BUILDR-476:
---------------------------------------
So we need to support mirrors for repositories, with either a binding from the mirror to the repo, or a global mirror.
To whoever wants to take over this one, let's discuss the API for it first so that it's slick :)
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (BUILDR-476) Buildr doesn't respect company
repository manager
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888516#action_12888516 ]
Alex Boisvert commented on BUILDR-476:
--------------------------------------
3-liner suggestion: monkey-patch repositories.remote in local .buildr file so it emits a warning and ignores additional repos.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.