[
https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731759#action_12731759
]
Assaf Arkin commented on BUILDR-288:
------------------------------------
I don't see how users getting from 'buildr is being slow and misbehaving' to 'I
need to clear repositories.remote' is a) intuitive and/or b) obvious.
I would say in reverse. This is a non-issue if you start with an existing
buildfile and replicate it on each new project (what I do), or just run the
buildr command and let it generate a buildfile for you. For the people who
don't do either *and* want to use the canonical repository as their first
remote repository, we're saving one explicit definition by replacing it with
magic.
And while each DRY is good and welcome, no matter how little, I think this one
is too little gain to just go breaking builds.
> 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.
