deprecated says to use pair and so it's used in the body
Javadoc changes
Use string interpolation and replace deprecated methods
Add a pending test for sbt/sbt#1142

Add a scripted test documents the current behavior of incremental
compiler when it comes to handling of inherited macros. A whitespace
change to a file that inherits a macro triggers recompilation of all files that
depend (by composition or inheritance) on that file.
Classes that only inherit a macro don't have a macro

Prior to this commit, a class that inherited a macro from another
class was considered by incremental compiler as having a macro.
Now, only classes that explicitly define a macro are considered as having
a macro. This influences decision whether to invalidate (recompile)
dependencies of a file that inherits a macro upon a whitespace change.
From now on, we don't invalidate dependencies in such case which
results in much better incremental compiler experience when macros are
being involved. Check #1142 for detailed discussion.

The change to the behavior is reflected by marking the
source-dependencies/inherited-macros test as passing.
The source-dependencies/macro test covers the case of defining the macro
directly in source file. Therefore we know that the desired behavior of
invalidating dependencies of macros is preserved.

Fixes #1142
Merge pull request #1202 from Duhemm/inherited-macros

Disable macro heuristic for inherited macros (sbt/sbt#1142)
Fix URITests to work under Windows
Merge pull request #1230 from dansanduleac/uri-tests

Fix URITests to work under Windows
Ensure that if artifact is published, we overwrite default checksums.

Fixes # 1233

* Add a new "shim" for RepositoryResolvers that modifies the "put"
  method so that it will ignore the overwrite flag for checksums.
Remove JDK7 features from Resolver shim.
Roll back sbt/sbt@482f99 (aggressive deletion of cache). Fixes #1091.

* sbt 0.12.3 introduced sbt/sbt@482f99 to fix #637 and #641.
* The underlying issue of #641 was an incorrect classifier, and it was
  fixed in sbt/sbt@718fa9 for #683 and shipped as sbt 0.13.0.
Merge pull request #1234 from sbt/wip/undo-nonsnapshot-deletion

Roll back aggressive deletion of cache. Fixes #1091.
Add two pending tests for sbt/sbt#1237

Add two scripted tests that illustrate a problem occurring with Scala 2.11-RC3
where some macros have themselves attached as original tree, which causes a
stack overflow during dependency extraction.
Handle macros that have themselves as original tree

It has been reported in sbt/sbt#1237 that stack overflows may occur during the
extraction of used names (and later of dependencies between files). This
problem has been introduced by sbt/sbt#1163, which was about recording the
dependencies of macro arguments.

When a macro is expanded, the compiler attaches the tree before expansion to
the tree representing the expanded macro. As of Scala 2.11-RC3, some macros
have themselves attached as original tree, which caused the same macro to be
inspected over and over until a stack overflow.

This commit solves this problem by making sure that the original of a macro
expansion will be inspected if and only if it is different from the expanded
tree.

Fixes sbt/sbt#1237
Merge pull request #1064 from jaceklaskowski/javadoc-changes

Javadoc changes
Merge pull request #1065 from jaceklaskowski/string-interpolation-follow-deprecation

Use string interpolation and replace deprecated methods
Merge pull request #1232 from sbt/wip/fix-1156

Ensure that if artifact is published, we overwrite default checksums.
Merge branch '0.13' into follow-deprecation
Follow deprecation - @deprecated says to use pair and so it's used in the body
Part #1 of cancel-task-hooks - Hooks EvaluateTask.

* Create a new EvaluateTaskConfig which gives us a bit more freedom
  over changign config options to EvaluateTask in the future.
* Create adapted from old EvaluateTask to new EvaluateTask
* Add hooks into signals class to register/remote  a signal listener
  directly, rather than in an "arm" block.
* Create TaskEvaluationCancelHandler to control the strategy of
  who/whom can cancel (sbt-server vs. sbt-terminal).
* Create a null-object for the "can't cancel" scenario so the
  code path is exactly the same.

This commit does not wire settings into the build yet, nor does it
fix the config extractio methods.