gradle

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add support for Java modules in Eclipse dependencies (#12694)

The Java module detection service is used to set the 'module=true'

attribute on Eclipse classpath entries that represent Java modules.

This will give use a similar behavior to Gradle's compile task

in Eclipse.

  1. … 12 more files in changeset.
Add support for Java modules in Eclipse dependencies

The Java module detection service is used to set the 'module=true'

attribute on Eclipse classpath entries that represent Java modules.

This will give use a similar behavior to Gradle's compile task

in Eclipse.

  1. … 12 more files in changeset.
Add support for Java modules in Eclipse dependencies

The Java module detection service is used to set the 'module=true'

attribute on Eclipse classpath entries that represent Java modules.

This will give use a similar behavior to Gradle's compile task

in Eclipse.

  1. … 12 more files in changeset.
Add support for Java modules in Eclipse dependencies

The Java module detection service is used to set the 'module=true'

attribute on Eclipse classpath entries that represent Java modules.

This will give use a similar behavior to Gradle's compile task

in Eclipse.

  1. … 12 more files in changeset.
Add support for Java modules in Eclipse dependencies

The Java module detection service is used to set the 'module=true'

attribute on Eclipse classpath entries that represent Java modules.

This will give use a similar behavior to Gradle's compile task

in Eclipse.

  1. … 12 more files in changeset.
Add support for Java modules in Eclipse dependencies

The Java module detection service is used to set the 'module=true'

attribute on Eclipse classpath entries that represent Java modules.

This will give use a similar behavior to Gradle's compile task

in Eclipse.

  1. … 12 more files in changeset.
Force AbstractTestDirectoryProvider to use Class (#12431)

Closes https://github.com/gradle/gradle-private/issues/2988

This PR adds `className` to `AbstractTestDirectoryProvider` so there'll be no more `unknown-test-class`.

    • -1
    • +1
    ./plugins/ide/idea/model/PathFactoryTest.groovy
  1. … 396 more files in changeset.
Fix more construtors

  1. … 3 more files in changeset.
Fix tests

    • -1
    • +1
    ./plugins/ide/idea/model/PathFactoryTest.groovy
  1. … 362 more files in changeset.
Do not add annotation processor classpaths to IDEA scopes (#12353)

In general this is wrong but it was done to enable older IDEA

versions to pick up the annotation processors (#7067).

There is no need for this anymore.

    • -2
    • +2
    ./plugins/ide/idea/IdeaPluginTest.groovy
  1. … 2 more files in changeset.
Do not add annotation processor classpaths to IDEA scopes

In general this is wrong but it was done to enable IDEA to

pick up the annotation processors (#7067). There should be no need

for this anymore.

    • -2
    • +2
    ./plugins/ide/idea/IdeaPluginTest.groovy
  1. … 1 more file in changeset.
Remove localGroovy() sources resolution in IDEs

  1. … 16 more files in changeset.
Properly isolate tests from the Gradle user home

When running Gradle, we use the current working directory as the

base directory for searching a `settings.gradle` file. For tooling

API tests this working directory is the one of Gradle itself, which

causes a number of issues because the root directory of the project

doesn't match the working directory.

Therefore, Gradle finds the `settings.gradle` file of its own build,

instead of finding the one in the test.

As a workaround, TAPI tests now use an action which will set the

working directory to the test directory, which should cover most

cases. Additional cases like missing settings files in projects

under tests have to be handled separately, as demonstrated in this

commit for the ProjectBuilder test.

  1. … 6 more files in changeset.
Properly isolate tests from the Gradle user home

When running Gradle, we use the current working directory as the

base directory for searching a `settings.gradle` file. For tooling

API tests this working directory is the one of Gradle itself, which

causes a number of issues because the root directory of the project

doesn't match the working directory.

Therefore, Gradle finds the `settings.gradle` file of its own build,

instead of finding the one in the test.

As a workaround, TAPI tests now use an action which will set the

working directory to the test directory, which should cover most

cases. Additional cases like missing settings files in projects

under tests have to be handled separately, as demonstrated in this

commit for the ProjectBuilder test.

  1. … 6 more files in changeset.
Properly isolate tests from the Gradle user home

When running Gradle, we use the current working directory as the

base directory for searching a `settings.gradle` file. For tooling

API tests this working directory is the one of Gradle itself, which

causes a number of issues because the root directory of the project

doesn't match the working directory.

Therefore, Gradle finds the `settings.gradle` file of its own build,

instead of finding the one in the test.

As a workaround, TAPI tests now use an action which will set the

working directory to the test directory, which should cover most

cases. Additional cases like missing settings files in projects

under tests have to be handled separately, as demonstrated in this

commit for the ProjectBuilder test.

  1. … 6 more files in changeset.
Create static instance of NullGradleApiSourcesResolver

  1. … 3 more files in changeset.
Download local-groovy sources when using an IDE

  1. … 10 more files in changeset.
Attach gradleApi() sources to IDE models (#11751)

Attach sources to gradleApi() and gradleTestKit() generated jars in the IDE models when -all distribution is used and sources are available.

  1. … 16 more files in changeset.
Attach API sources without packaging them in a jar

  1. … 14 more files in changeset.
Use Gradle's file API for visiting sources for zipping

It ensures that paths are returned in unix format.

  1. … 12 more files in changeset.
Sort sources prior to zipping

The source tree is returned in different order depending on the file system - we do not want to depend on that.

  1. … 1 more file in changeset.
Use Java7 API for constructing a Path

Use Windows friendly path assertions

  1. … 3 more files in changeset.
Attach gradleApi() sources to IDE model

  1. … 11 more files in changeset.
Move the builder to internal API

    • -0
    • +22
    ./plugins/ide/internal/tooling/vfs/InvalidateVirtualFileSystemLocationsBuilderTest.groovy
    • -22
    • +0
    ./plugins/ide/vfs/InvalidateVirtualFileSystemLocationsBuilderTest.groovy
  1. … 5 more files in changeset.
Add a tooling API model invalidates the VFS

    • -0
    • +22
    ./plugins/ide/vfs/InvalidateVirtualFileSystemLocationsBuilderTest.groovy
  1. … 8 more files in changeset.
Add system property to remove tasks from GradleProject model

  1. … 1 more file in changeset.
Revert "Introduce 'annotationProcessorClasspath' configuration"

This reverts commit 444a899c9cf4c968ce6a490d8148f35a1d631795 and

follow up changes to the annotation processing configurations.

    • -2
    • +2
    ./plugins/ide/idea/IdeaPluginTest.groovy
  1. … 11 more files in changeset.
Introduce 'annotationProcessorClasspath' configuration

    • -2
    • +2
    ./plugins/ide/idea/IdeaPluginTest.groovy
  1. … 9 more files in changeset.
Introduce 'annotationProcessorClasspath' configuration

    • -2
    • +2
    ./plugins/ide/idea/IdeaPluginTest.groovy
  1. … 9 more files in changeset.