[
https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731028#action_12731028
]
Alex Boisvert commented on BUILDR-288:
--------------------------------------
I agree this is equivalent to changing API behavior. The proper way to deal
with this is to document the change in the release notes so that people who
upgrade learn about the change before it happens to them.
Our backward compatibility guidelines
(http://cwiki.apache.org/confluence/display/BUILDR/Backward+Compatibility) say
that we should maintain backward compatibility for at least one minor version.
Does this mean that since this behavior hasn't changed since 1.2.x we would be
within the guidelines?
> 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.
