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/06/19 22:24:07 UTC
[jira] Created: (BUILDR-288) Add Canonical Maven2 Repository by
Default
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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731000#action_12731000 ]
Alex Boisvert commented on BUILDR-288:
--------------------------------------
+1 from me on pushing this into trunk.
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Daniel Spiewak (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Nicholas Tung (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735461#action_12735461 ]
Nicholas Tung commented on BUILDR-288:
--------------------------------------
What about prompting the user if the build fails, and they just imported a Maven build file?
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Daniel Spiewak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722912#action_12722912 ]
Daniel Spiewak commented on BUILDR-288:
---------------------------------------
Well, as far as I'm aware, *every* dependency management tool which makes use of Maven2 metadata has the canonical upstream in its default repositories list -- except for Buildr. As far as the "principle of least surprise" goes, I think default inclusion would be the obvious choice.
As far as damage control when this causes something to go wrong, I users would probably be OK with figuring out what went wrong. This again comes back to the "least surprising" defaults. Most people will *expect* Buildr to include the canonical repository, and thus will plan accordingly. When something goes wrong due to the default repository list, I imagine that will be one of the first things they think of.
It is something we would have to document though. I don't think this is a change we can silently shove into the CHANGELOG and forget all about it.
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731759#action_12731759 ]
Assaf Arkin commented on BUILDR-288:
------------------------------------
I don't see how users getting from 'buildr is being slow and misbehaving' to 'I need to clear repositories.remote' is a) intuitive and/or b) obvious.
I would say in reverse. This is a non-issue if you start with an existing buildfile and replicate it on each new project (what I do), or just run the buildr command and let it generate a buildfile for you. For the people who don't do either *and* want to use the canonical repository as their first remote repository, we're saving one explicit definition by replacing it with magic.
And while each DRY is good and welcome, no matter how little, I think this one is too little gain to just go breaking builds.
> 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.
[jira] Resolved: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Antoine Toulme (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme resolved BUILDR-288.
-----------------------------------
Resolution: Won't Fix
Marking as won't fix, with known workaround: rtfm
> 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
>
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731100#action_12731100 ]
Assaf Arkin commented on BUILDR-288:
------------------------------------
Of should and would, I'm only concerned with would. If Buildr 1.3.5 was all of a sudden slow uploading artifacts, or failing more often because it's starting with the wrong repository, I would just blame it on Buildr 1.3.5 being worse than the previous release. I would not be heading to the artifacts section, and remember that my mental model is that I add all repositories explicitly, the last thing I'm going to notice or think of as the root problem, is anything that contradicts my mental model.
I say we don't do it in a point release, it's a breaking change and we should treat it as such. We can use the next release to start warnings that the default behavior will change, so developers get a change to guard their buildfile against future updates.
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Daniel Spiewak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731009#action_12731009 ]
Daniel Spiewak commented on BUILDR-288:
---------------------------------------
Any objections, Assaf? Otherwise, I'll dcommit my changes (including documentation).
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Daniel Spiewak (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731063#action_12731063 ]
Assaf Arkin commented on BUILDR-288:
------------------------------------
I think you're assuming a level of involvement with Buildr documentation/details that's reflective of dev-, not the general population. For most people Buildr is just a tool, not the life of the party. I gem update often, hardly ever check the changelog, mailing list or RTFM. I just hope it will keep working or break in obvious ways. When you get a lot of people using a tool, you can assume that's the default behavior.
If this was an API change and we followed the guidelines, we would announce the old behavior is deprecated in 1.3.5 (or 1.4), remove it completely in 1.5. For the duration of 1.4.x you'd be able to use the old feature (with warnings) while transitioning to the new one. Ode, for example, was building with warnings for months, using newer version of Buildr with older buildfile. My guess is most projects are like Ode, not in a hurry to catch up on the latest releases.
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731014#action_12731014 ]
Assaf Arkin commented on BUILDR-288:
------------------------------------
"As far as damage control when this causes something to go wrong, I users would probably be OK with figuring out what went wrong."
How would you figure out what went wrong?
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.
But if this change happens in memory, it's the first repository Buildr looks at, and there's nothing indicating that -- how would you go about figuring it? Let's say I have a clone of the Maven repo on my network with faster access. I put it first on the list. Except Buildr goes and chekcs with maven.org first because of this feature I'm unaware of. Sometimes I can't tell the difference. Sometimes it's dog slow -- is it Buildr acting up? my clone of Maven repo just not that good?
a) How do we make this behavior visible?
b) How do we roll this change out?
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.
> 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.
[jira] Updated: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated BUILDR-288:
---------------------------------
Fix Version/s: (was: 1.3.5)
> 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
>
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Assaf Arkin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731108#action_12731108 ]
Assaf Arkin commented on BUILDR-288:
------------------------------------
BTW the current behavior is a feature that can be deprecated:
"Buildr does not include canonical Maven2 repository by default"
>From an API perspective, in the current behavior repositories.remote is initialized to an empty set, in the new behavior repositories.remote.should include(m2_canonical_url).
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Daniel Spiewak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731133#action_12731133 ]
Daniel Spiewak commented on BUILDR-288:
---------------------------------------
Alright. I don't like it, but deferral does seem like the more prudent course of action. How do we deprecate the current behavior? I mean, how do we detect when to issue the warning?
> 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Daniel Spiewak (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (BUILDR-288) Add Canonical Maven2 Repository by
Default
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731164#action_12731164 ]
Alex Boisvert commented on BUILDR-288:
--------------------------------------
I think we're making a big fuss about this. If Buildr was all of a sudden much slower to download artifacts, or failing more often, I would see clearly that it's downloading from repo1.maven.org. And if seeing repo1.maven.org surprises me, then I'd be quick to print out repositories.remote and change it to suit my preferences.
> 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.