buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Assaf Arkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by Default
Date Tue, 23 Jun 2009 00:22:07 GMT

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

Assaf Arkin commented on BUILDR-288:
------------------------------------

Changing the default could be good -- if you meant to do it anyway -- or bad if you don't
want to use stuff from maven.org and you might not be aware it's happening because dependencies
that should fail now "silently succeed". It's possible to remove, but it's likely that people
will not remove that which silently succeeds, and so the question is "how bad would it for
some people to accidentally get code from maven.org"?

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


Mime
View raw message