[
https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722912#action_12722912
]
Daniel Spiewak commented on BUILDR-288:
---------------------------------------
Well, as far as I'm aware, *every* dependency management tool which makes use
of Maven2 metadata has the canonical upstream in its default repositories list
-- except for Buildr. As far as the "principle of least surprise" goes, I
think default inclusion would be the obvious choice.
As far as damage control when this causes something to go wrong, I users would
probably be OK with figuring out what went wrong. This again comes back to the
"least surprising" defaults. Most people will *expect* Buildr to include the
canonical repository, and thus will plan accordingly. When something goes
wrong due to the default repository list, I imagine that will be one of the
first things they think of.
It is something we would have to document though. I don't think this is a
change we can silently shove into the CHANGELOG and forget all about it.
> 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.
