[
https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731100#action_12731100
]
Assaf Arkin commented on BUILDR-288:
------------------------------------
Of should and would, I'm only concerned with would. If Buildr 1.3.5 was all
of a sudden slow uploading artifacts, or failing more often because it's
starting with the wrong repository, I would just blame it on Buildr 1.3.5 being
worse than the previous release. I would not be heading to the artifacts
section, and remember that my mental model is that I add all repositories
explicitly, the last thing I'm going to notice or think of as the root problem,
is anything that contradicts my mental model.
I say we don't do it in a point release, it's a breaking change and we should
treat it as such. We can use the next release to start warnings that the
default behavior will change, so developers get a change to guard their
buildfile against future updates.
> 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.
