Merge branch '2.10.2' into 2.10.3

Conflicts:
	src/compiler/scala/tools/nsc/typechecker/NamesDefaults.scala
Merge pull request #2878 from JamesIry/2.10.3

Merge 2.10.2 into 2.10.3
update typesafe.artifactory-online.com to private-repo
Change Scala license to unmodified 3-clause BSD.

No longer using the slightly reworded 3-clause BSD license.
This does not change the meaning of the license,
just aligns it with the standard wording.
Merge remote-tracking branch 'origin/2.10.x' into merge/2.10.x-to-2.10.3
SI-7815 Dealias before deeming method type as dependent

To enable eta-expansion of method types seen from a prefix that
renders the result type as independent from the parameter symbols.

The enclosed test shows that we dealias types before checking
dependence, and that we do this deeply (e.g. type arguments are
also dealised.)

An existing test, neg/error_dependentMethodTpeConversionToFunction,
confirms that bona-fide dependent methods are still prohibited from
eta expansion.
SI-7825 Consider DEFAULTMETHOD when refchecking concreteness

A class should not be required to implement a Java default method.

This commit uses `isDeferredNotDefault` in place of `isDeferred`
when finding unimplemented methods.

The test itself does not depend on Java 8 as we use scalac's
Java source parser to set things up.
SI-7398 Enable test for Java 8 source parser under Java 8

There is no need to skip it as it only depends on our changes
to our JavaParser, and not on any bytecode features of Java 8.
Merge pull request #2923 from retronym/ticket/7825

SI-7825 Consider DEFAULTMETHOD when refchecking concreteness
Merge pull request #2882 from adriaanm/license-cleanup-2.10.x

Change Scala license to unmodified 3-clause BSD.
Merge pull request #2893 from adriaanm/backport-2880-2.10.x

update typesafe.artifactory-online.com to private-repo
Merge remote-tracking branch 'origin/2.10.x' into merge/2.10.x-to-2.10.3
Merge pull request #2906 from retronym/merge/2.10.x-to-2.10.3

Merge/2.10.x to 2.10.3
Fix typo in documentation.
SI-7852 Test to show the status quo bytecode for "" == ...

Will be somewhat leaner after the next commit.
SI-7852 Omit null check for "".==

Although the same the code would be later optimized by -Yconst-opt,
we can offer the same lean byte code to those compiling without that
option by being more discerning when translating ==.

This helps people using bytecode based code coverage tools
such as jacoco that would emit "branch not covered" warnings
for the impossible null check.
SI-7852 Test to show status quo of for SomeModule.==

For which we can also elide the null check, and will in the
next commit.
SI-7848 Xlint says what looks interpolated

The motivating use case was an Expecty debug string
getting flagged for `$eq`.

The test case demonstrates a different bug, in which
the position of the literal tree is changed when typer
gets rid of the unused local, so that when the tree is
re-typed in erasure, a second, spurious warning is
emitted at the start of the method. Specifically, the
second warning is not suppressed because of the
different position.
Silence pos/t3960's -Ycheck output.

Someday someone will have to straighten out where output goes.
Clearly under current conditions, Console.err is not a good place.
I rerouted through unit.warning so the output will be swallowed
like all the other warnings.
Cull extraneous whitespace.

One last flurry with the broom before I leave you slobs to code
in your own filth. Eliminated all the trailing whitespace I
could manage, with special prejudice reserved for the test cases
which depended on the preservation of trailing whitespace.

Was reminded I cannot figure out how to eliminate the trailing
space on the "scala> " prompt in repl transcripts. At least
reduced the number of such empty prompts by trimming transcript
code on the way in.

Routed ConsoleReporter's "printMessage" through a trailing
whitespace stripping method which might help futureproof
against the future of whitespace diseases. Deleted the up-to-40
lines of trailing whitespace found in various library files.

It seems like only yesterday we performed whitespace surgery
on the whole repo. Clearly it doesn't stick very well. I suggest
it would work better to enforce a few requirements on the way in.