Call non-deprecated isRawType instead of isRaw
Ivy Artifact needs wildcard configuration added if no explicit ones are defined.  Fixes #439.
Add 3s sleep to dependency-management/cache-classifiers test to handle 1s last modified resolution.
Print the temporary base directory when pausing in a scripted test.
follow-up to invalidating changing artifacts: super.cacheModuleDescriptor can be null
Only include standard scopes in pom.xml.
update dependency in tests/test-quick for 2.10
update project/transitive-plugins test to use a common cache
Docs: no need to copy sources, which aren't used anywhere on the site
build with 0.12.2
Build: add includeTestDependencies key that can be used to temporarily turn off fetching test dependencies.
Remove InputStatic and parsedResult.

This cleans up the InputTask implementation.  It no longer requires the hook
in setting loading (Load.finalTransforms) and has better types.
Don't catch org.scalacheck.Prop.Exception
Fix compile error in Eclipse

Let's consider compile/inc/src/main/scala/sbt/CompileSetup.scala.
There are multiple Output types, and according to Eclipse importing
xsbti.compile.Output within the package sbt does not work because the
import is shadowed by sbt.Output.

However, compilation proceeds just fine within SBT. Reproducing the
example however gives the same warning, if the files are in the same
project. The problem here is probably that the shadowing Output
is declared in the same package but in another project, and that seems
to give different results in Eclipse and SBT, but relying on
that looks fragile.
Reading the spec is inconclusive since it doesn't match with Scalac's
behavior — see
https://groups.google.com/d/topic/scala-internals/-Rquc2HBYLk/discussion .

ForkTests has the same behavior as CompileSetup.
Silence boring Eclipse warnings: unused imports
Silence boring Eclipse warnings: @SuppressWarnings("rawtypes")

Add @SuppressWarnings("rawtypes") to ResolverAdapter, since it has a comment
making pretty clear that using raw types is intended.
Silence boring Eclipse warnings: catching all exceptions

Here I make explicit where catching all exceptions is intended.
Mark Harrah corrected one decision during review.
Silence boring Eclipse warnings: catching all exceptions, part 2

These warning fixes are new since my last pull request, please verify.
Silence boring Eclipse warnings: feature warnings - take #2

Silencing boring warnings allows seeing the interesting ones. Here I've excluded
reflectiveCalls, since that's a useful warning.
However, silencing those warnings in *Eclipse* would require committing Eclipse
projects, something which *will* take extra effort; I verified that the warnings
disappeared from the output of compilation in SBT.
Enable Java -Xlint warnings, excluding serialization-related ones