[
https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731080#action_12731080
]
Daniel Spiewak commented on BUILDR-288:
---------------------------------------
Well, the question is: how do we deprecate a non-feature? The functionality we
are breaking is the *lack* of functionality, so it's not like we can issue a
warning or anything like that. I agree that there is a large segment of users
who will just gem update and never look at the release notes, but I'm not sure
there is anything we can do about them. We can document this heavily, put it
in the release notes, announce it far and wide, but if people choose to ignore
our warnings of breakage, I think that's their responsibility. Even the gem
update crowd is going to at least test their buildfile after they upgrade.
Either things will work, in which case there is no problem, or they won't work,
in which case they will have to root the problem through. Their first stop on
the journey *should* be the artifacts documentation, at which point they will
see that maven.org is included by default and act accordingly.
On a side note, I strongly suspect that the only users who will see issues with
this change are also the folks who follow the Buildr releases a bit more
closely. At least, they're probably reading the change logs to make sure that
their custom mirroring strategy isn't going to be broken. Most users may not
notice the announcements, but if you filter those users down to the few who
will be negatively affected, I don't think you will have a very long list.
Newcomers to Buildr will be no trouble at all. Even assuming that they expect
the repositories list to be empty, the only way they will learn how to change
that list is by reading the documentation. You literally *cannot* read the
modified artifacts documentation without being warned about the default
inclusion, so information will not be an issue there.
So, I guess the question I have is: do we leave this (arguably) wrong behavior
forever just because of a small segment of inattentive users? Or, do we make
the improvement, announce it to the best of our ability, and trust that we're
doing the right thing?
> 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.
