[
https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731063#action_12731063
]
Assaf Arkin commented on BUILDR-288:
------------------------------------
I think you're assuming a level of involvement with Buildr
documentation/details that's reflective of dev-, not the general population.
For most people Buildr is just a tool, not the life of the party. I gem update
often, hardly ever check the changelog, mailing list or RTFM. I just hope it
will keep working or break in obvious ways. When you get a lot of people using
a tool, you can assume that's the default behavior.
If this was an API change and we followed the guidelines, we would announce the
old behavior is deprecated in 1.3.5 (or 1.4), remove it completely in 1.5. For
the duration of 1.4.x you'd be able to use the old feature (with warnings)
while transitioning to the new one. Ode, for example, was building with
warnings for months, using newer version of Buildr with older buildfile. My
guess is most projects are like Ode, not in a hurry to catch up on the latest
releases.
> 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.
