Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix backwards compatibility of new Java configurations

When a `java` or `java-library` project is referenced from another project

that doesn't know about the `usage` attribute, then all runtime dependencies

need to be exposed. This is necessary e.g. when packaging EARs or applications.

At the same time we want to have the minimal set of leaked dependencies for

consumers that do know about `usage`. The solution is to move the `apiElements`

configuration up to the `java` plugin and let it contain `compile` and `runtime`

for backwards compatibility. The `default` configuration contains everything on the

`runtimeClasspath`.

Once `compile` and `runtime` have been removed in some future Gradle version,

we will have exactly what we want: An empty API for `java` projects and only

exposing the `api` configuration for `java-library` projects.

Make checkstyle happy

Me thinks I make you happy much more often than you make me happy.

Signed-off-by: Cedric Champeau <cedric@gradle.com>

Add a couple of test cases

Signed-off-by: Cedric Champeau <cedric@gradle.com>

Add intermediate method `isAccessibleConstant` for clarity

Signed-off-by: Cedric Champeau <cedric@gradle.com>

Rename method for clarity

Signed-off-by: Cedric Champeau <cedric@gradle.com>

Fix typo

Signed-off-by: Cedric Champeau <cedric@gradle.com>

Rework API to have coordination work in a single place

Add missing `byte`

Signed-off-by: Cedric Champeau <cedric@gradle.com>

Rename `type` -> `modifier` for clarity

Signed-off-by: Cedric Champeau <cedric@gradle.com>

:arrow_up: Kotlin 1.1.0-beta-17 :tada:

Resolves #248

rename InternalBuildListener to InternalBuildOperationListener

  1. … 3 more files in changeset.
compileOnly notes updated

- Added a small description in the preamble.

- Corrected syntax and formatting in "Potential breaking changes".

    • -1
    • +4
    /subprojects/docs/src/docs/release/notes.md
Don't use native platform for Windows as we are seeing weird test failures

... that may be related to this. If failures go away it will confirm that

stat with native platform on Windows would be broken.

address more --scan story review items

- tweak test naming

- tweak error messages

- tweak build scan plugin detection to .BuildScanPlugin

+review REVIEW-6415

Fix incremental compiler to recognize changes made to types referenced in fields or method signatures

Merge pull request #1174 from gradle/so-java-library-test-usage

Make api/implementation work for testing too

Merge branch 'release'

Fix NPE in test retry rule

Merge pull request #1176 from gradle/so-fix-compile-only

Remove accidentaly `compileOnly extendsFrom compile`

    • -0
    • +3
    /subprojects/docs/src/docs/release/notes.md
Add github issue reference to test method

Rename test method

Use URLClassloader to simulate faulty classloaders

Fix whitespace

Added more test coverage for compile avoidance.

Fix benchmark referencing old types

Add @since tag to new API methods in ResolutionStrategy

gradle/performance#203

Mark two tasks as @NotYetImplemented

+review REVIEW-6424

ignore tests temporarily

Fix application plugin test that put files into build/ before the test runs

+review REVIEW-6424

Fix idea test that created generated resources before the build ran

+review REVIEW-6424