[
https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731164#action_12731164
]
Alex Boisvert commented on BUILDR-288:
--------------------------------------
I think we're making a big fuss about this. If Buildr was all of a sudden much
slower to download artifacts, or failing more often, I would see clearly that
it's downloading from repo1.maven.org. And if seeing repo1.maven.org surprises
me, then I'd be quick to print out repositories.remote and change it to suit my
preferences.
> Add Canonical Maven2 Repository by Default
> ------------------------------------------
>
> Key: BUILDR-288
> URL: https://issues.apache.org/jira/browse/BUILDR-288
> Project: Buildr
> Issue Type: Improvement
> Components: Dependency management
> Reporter: Daniel Spiewak
> Fix For: 1.3.5
>
>
> Almost every buildfile I have ever created starts with the following line:
> repositories.remote << 'http://repo1.maven.org/maven2'
> We already add the scala-tools.org repository to the list when 'buildr/scala'
> is required, so why not the official, canonical repository at maven.org? I
> think that new users especially would find this more intuitive. There is no
> real loss of flexibility since it is always possible to *remove* a repository
> from the array if it becomes necessary.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
