gradle

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>

This will permit a single `ResolvedVersionConstraint` to have both a `prefer`

and a `require` version.

Signed-off-by: Paul Merlin <paul@gradle.com>

`Class.newInstance()` was deprecated in Java 9.

This commit fixes artifact selection so that when we resolve artifacts, we also use

the attributes defined on the dependency itself, if ever. Before, when we were resolving

artifacts, only the consumer configuration attributes were used.

The 'resolved' version constraint is critical to resolving the component id

for a given selector. In order to honour all constraints in the resolution

process, this `ResolvedVersionConstraint` will be composed of more than

just the constraints for a single selector.

With this change, the `ResolvedVersionConstraint` is constructed

prior to resolving the id, rather than being constructed as part of that

process.

This commit pre-computes a `ModuleIdentifier` from a dependency and passes it around several places where it

is used. This saves a bunch of lookups in the module identifier cache, which tend to be pretty expensive.

Dependency substitution is also passed the original module identifier, in case no substitution is done. This

prevents an additional lookup.

This commit bumps the ASM library used in Gradle from 5.1 to 6.0_ALPHA. While being an alpha version, this ASM version is the only

one compatible with the Java 9 class format. This allows us to remove the `Java9ClassReader`, and also makes it possible to re-enable

some tests which were failing due to mocking bugs under JDK 9.

- setDependencyCacheDir in java plugin and CompileOptions

- Use of Ant <depend> task and Depend options

- Javadoc setOptions

- Manifest.writeTo(Writer)

- JavaPluginConvention.setProject

Issue: #1722

This change allows us to use `select` instead of `transform` as the

action method and should also locate uses/implementations of this

interface.

Also added a bunch of test coverage for `@CompileClasspath`.

Instead of sorting the files after reading them from disk we

use `ReproducibleDirectoryWalker` to directly read them from disk in

a reproducible way independent of the file system.

This has the advantage that we do not add some special handling for

zipTree and tarTree. It probably has some performance impact when

having walking the file system but the impact should actually be

less than sorting afterwards since we sort smaller lists and we do

not need to keep all the file names in an archive in memory.