Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Reorder versions so the default version is first

Recognize contributor

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Merge remote-tracking branch 'origin/sg/61/upgrade-guide'

* origin/sg/61/upgrade-guide:

Add a new migration guide for 6.x and move compatibilty to its own section

Render a clickable link when dead links are detected

Try to make Scala compilation work with Zinc 1.3.0

    • -2
    • +2
    /subprojects/docs/src/docs/release/notes.md
Merge branch 'fix-for-zinc-1.3.0' of https://github.com/snazy/gradle into release

* 'fix-for-zinc-1.3.0' of https://github.com/snazy/gradle:

Let Gradle 6.0 work with Zinc 1.3.0

Update test coverage matrix for Jacoco

Recognize contributor

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Update released version to latest snapshot

Clean accepted API changes

Update version to 6.2

Rebaseline RealWorldNativePluginPerformanceTest

See https://github.com/gradle/gradle-private/issues/2793 for details.

Fix typo (#11029)

Signed-off-by: Steven Spungin <steven@spungin.tv>

Merge branch 'release'

Update released version to latest snapshot

Clean accepted API changes

Update version to 6.2

Merge remote-tracking branch 'origin/master-test' into release-test

Fix test

Publish 6.0-20191014000926+0000

Disallow `buildSrc` as the name of an included build

Except for the actual buildSrc build

Restore < Gradle 6 buildSrc location when using custom root project dir

Previously, we used ${settings.rootDir}/buildSrc, but this was evaluated

before the settings file. So, if the user changed the root dir location

we were unaffected. Now that settings is evaluated first, we looked in a

different place. Strike one more for silent mutability.

Publish 6.0-20191013230024+0000

Fix edge case for class display names

Simply using the class display name in test logging does not work,

because JUnit platform returns only the simple class name from

TestIdentifier.getDisplayName(). This results in the fully qualified

package name being cut off for top level classes.

This change adds some logic that tried to find out whether the display

name has been explicitly se tor not. If so then the class display name

will we use. If not the fully qualified class name will be used for top

level classes and the simple class name will be used for inner classes.

There is still one corner case that is not supported with this solution:

A user could set the simple class name as display name in order to remove

the package name from the output. Since there is no way to tell whether

this was explicitly configured by the user or not by looking at the

TestIdentifier, there does not seem to be a way to support this.

Fix edge case for class display names

Simply using the class display name in test logging does not work,

because JUnit platform returns only the simple class name from

TestIdentifier.getDisplayName(). This results in the fully qualified

package name being cut off for top level classes.

This change adds some logic that tried to find out whether the display

name has been explicitly se tor not. If so then the class display name

will we use. If not the fully qualified class name will be used for top

level classes and the simple class name will be used for inner classes.

There is still one corner case that is not supported with this solution:

A user could set the simple class name as display name in order to remove

the package name from the output. Since there is no way to tell whether

this was explicitly configured by the user or not by looking at the

TestIdentifier, there does not seem to be a way to support this.

Fix edge case for class display names

Simply using the class display name in test logging does not work,

because JUnit platform returns only the simple class name from

TestIdentifier.getDisplayName(). This results in the fully qualified

package name being cut off for top level classes.

This change adds some logic that tried to find out whether the display

name has been explicitly se tor not. If so then the class display name

will we use. If not the fully qualified class name will be used for top

level classes and the simple class name will be used for inner classes.

There is still one corner case that is not supported with this solution:

A user could set the simple class name as display name in order to remove

the package name from the output. Since there is no way to tell whether

this was explicitly configured by the user or not by looking at the

TestIdentifier, there does not seem to be a way to support this.

Fix edge case for class display names

Simply using the class display name in test logging does not work,

because JUnit platform returns only the simple class name from

TestIdentifier.getDisplayName(). This results in the fully qualified

package name being cut off for top level classes.

This change adds some logic that tried to find out whether the display

name has been explicitly se tor not. If so then the class display name

will we use. If not the fully qualified class name will be used for top

level classes and the simple class name will be used for inner classes.

There is still one corner case that is not supported with this solution:

A user could set the simple class name as display name in order to remove

the package name from the output. Since there is no way to tell whether

this was explicitly configured by the user or not by looking at the

TestIdentifier, there does not seem to be a way to support this.

Invert dependency between getDisplayName() and getClassDisplayName()

Invert dependency between getDisplayName() and getClassDisplayName()

Invert dependency between getDisplayName() and getClassDisplayName()

Update released version to latest snapshot