You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Daniel Spiewak (JIRA)" <ji...@apache.org> on 2009/07/14 08:03:14 UTC

[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by Default

    [ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730709#action_12730709 ] 

Daniel Spiewak commented on BUILDR-288:
---------------------------------------

What are the current thoughts on this matter?  I've been using Buildr with the modification for a while now without any ill-effects.  Though, as we agreed, the biggest change effect here is in the area of user expectation.  I'm of the opinion that we should just push this into trunk/, document and see what happens.

> 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.