Jendrik Johannes

Add experimental distributed build plugin

  1. … 5 more files in changeset.
Add experimental distributed build plugin

  1. … 5 more files in changeset.
Add experimental distributed build plugin

Add experimental distributed build plugin

  1. … 5 more files in changeset.
Add experimental distributed build plugin

  1. … 5 more files in changeset.
Add experimental distributed build plugin

Add experimental distributed build plugin

Add experimental distributed build plugin

  1. … 5 more files in changeset.
No special treatment of milestone versions when calculating next major (#7908)

A special treatment was added for Gradle 1.0. This did assume that

there will be no milestones for minor releases. This was an issue with

5.1-milestone-1, which is a minor release milestone.

Since the special treatment is not necessary for any milestone release

(major or minor) anymore, we remove it.

Start remote builds on agents through Jenkins

Tweaks for demonstration

Tweaks for demonstration

Tweaks for demonstration

Expand test tasks to have a task variant for each environment

Expand test tasks to have a task variant for each environment

Add initial experimental distributed build plugin

Add initial experimental distributed build plugin

No special treatment of milestone versions when calculating next major

A special treatment was added for Gradle 1.0. This did assume that

there will be no milestones for minor releases. This was an issue with

5.1-milestone-1, which is a minor release milestone.

Since the special treatment is not necessary for any milestone release

(major or minor) we remove it.

No special treatment of milestone versions when calculating next major

A special treatment was added for Gradle 1.0. This did assume that

there will be no milestones for minor releases. This was an issue with

5.1-milestone-1, which is a minor release milestone.

Since the special treatment is not necessary for any milestone release

(major or minor) we remove it.

Configure java test srcDirs as test source folders in IDEA

Otherwise, the groovy folder configuration is ignored.

Do not configure delegation to Gradle during IDEA import

Developers work with both delegating (currently still has some issues)

and not delegating to Gradle. Configuring this during import overrides

the individual settings. We do not want that anymore.

Add comments to IDEA import workarounds in build scripts

Clarify IDEA import workaround

Improve script readability

Merge pull request #7768 from gradle/jjohannes/dev-prod/idea-sync

Fix IDEA import for gradle/gradle with 'one module per source set' option

Revert "Do not add Gradle out folders as source folders to IDEA when using Sync"

This reverts commit 5d47f9be477247f5b972cbe051e94eb88adf5fda.

Improved comment

Improved script code readability

Always register the 'copySamples' task

Fix classpath construction in module registry for running tests in IDEA

The classpath is filtered by name matching. The subproject `resources`

caused problems, because one of the suffixes is

`/out/production/resources`, which matched the `resources` folders

in all subprojects (e.g. it matched `/ide/out/production/resources`).