Gradle 6.1 軟體 Download 下載

• 1

  版本確認

• 2

  檔案準備中

• 3

  檔案下載

What's new in this version:

Improvements for plugin authors:
- Finalize property value only when the value is queried
- In previous Gradle releases, certain Gradle types, such as Property or ConfigurableFileCollection, provided a finalizeValue() method that eagerly calculated the final value for a property and prevented further changes
- When a task starts running, Gradle automatically finalizes task properties of these types, so that the same value is seen by the task's actions and Gradle's build caching/up-to-date checks. This also avoids calculating the property value multiple times, which can sometimes be expensive. Plugins can also use finalizeValue() to finalize other properties, such as a property of a project extension, just prior to querying the value.
- In this release, these types gain a new finalizeValueOnRead() method. This method is similar to finalizeValue(), except that the final value is calculated when the value is queried rather than immediately. Plugins can use this method when a property value may be expensive to calculate or when the value may not have been configured to ensure that all consumers of the property see the same, final, value from that point onwards.
- Please see the user manual for more details

New managed property types:
- Gradle 5.5 introduced the concept of a managed property for tasks and other types, where Gradle provides an implementation of the getter and setter for an abstract property defined on a task, project extension, or other custom type. This simplifies plugin implementations by removing a bunch of boilerplate.
In this release, it is possible for a task or other custom type to have an abstract read-only property of type DomainObjectSet<T>.
- Please see the user manual for more details.

New factory methods:
The ObjectFactory type, which plugins and other custom types use to create instances of various useful types, has several new factory methods to create certain Gradle types that could only be created using internal APIs in previous releases:
- The polymorphicDomainObjectContainer() method to create ExtensiblePolymorphicDomainObjectContainer<T> instances
- The namedDomainObjectSet() method to create NamedDomainObjectSet<T> instances
- The namedDomainObjectList() method to create NamedDomainObjectList<T> instances

Improvements for Gradle tooling providers:
- Tooling API: TestLauncher can run specific Test task tests
- The TestLauncher interface in the Tooling API could already launch tests by specifying the name of the test classes or methods; however, if there are multiple Test tasks, then all Test tasks would be executed.
- For IDEs, developers usually want to execute only one task at a time. Gradle 6.1 introduces a new API to execute tests with specific Test task using the withTaskAndTestClasses() and withTaskAndTestMethods() methods.