[
https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731029#action_12731029
]
Daniel Spiewak commented on BUILDR-288:
---------------------------------------
IIRC, running Buildr with the --trace option will show which repositories are
being checked. This would be a fairly easy way for people to dig into what's
going on, though it would need to be made more widely known. As for the local
clone bit, I put particular emphasis on unshift-ing the repositories array in
the documentation. I think if people see mysterious behavior, what I've
written should explain most of what happens. Incidentally, just so there's no
ambiguity as to what I'm proposing, I have pushed my BUILDR-288 branch up to my
Git fork.
> If you let Buildr generate the buildfile, it adds a default repository to the
> file (except it points to ibiblio, should this be fixed?) and you get default
> behavior that's obvious.
We probably shouldn't be using the Ibiblio mirror by default. It's sometimes
faster than maven.org, but it also lags behind a bit and occasionally even
lacks some artifacts that are in the canonical repo. Critically though, I
think Maven points to maven.org by default, defining that as "expected
behavior".
a) Documentation, documentation, documentation. When I was a newcomer to
Buildr, it was always extremely surprising to me that the default Maven repo
was *not* included. Even if we don't choose to include it by default, we
absolutely need to document this behavior more closely.
b) We've talked about making the next release 1.4. People expect breaking
changes in large release number jumps. I think we just push it into trunk,
announce it on the users list, mention it in the changelog and be done with it.
> Remember that if this feature is on by default, it's effectively changing how
> existing buidlfiles behaves. It's the equivalent of changing API behavior.
Agreed. This isn't something I'm proposing lightly. However, I really do
believe that the current behavior (no default) is much less intuitive than the
proposed patch, particularly in light of things like Scala support including
the scala-tools.org repo automatically.
> 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.
