Github user steveloughran commented on the issue:
https://github.com/apache/spark/pull/14646
I'd be against making it default for a few reasons
1. You don't want to accidentally pick up some staging artifact or upstream
snapshot.
2. I don't know how SBT/Ivy handles remote staging artifact location;
having looked through existing JIRAs related to differences between SBT and
maven repositories, I didn't want to diverge things.
3. If you are doing local dev of upstream code, it's actually a real pain
when a build suddenly decides to get a remote snapshot of an artifact which you
haven't built locally that day. You generally do prefer the build to halt than
for it to pick up some remote snapshot which doesn't have your code in. Best
bit: maven will do this inside a project itself if the build spans midnight.
Keeping it isolated avoids that.
What I could do is add a section on this to the building-spark doc, to
avoid people having to read through the POM to find it
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
