Gradle 7.3 軟體 Download 下載

檔案名稱 gradle-7.3-all.zip

Gradle 7.3 軟體下載

軟體資訊
檔案版本 Gradle 7.3

檔案名稱 gradle-7.3-all.zip
檔案大小
更新日期 2021-11-10
  • 1
    版本確認
  • 2
    檔案準備中
  • 3
    檔案下載

軟體介紹 & 更新資訊

Gradle 7.3
VMware Workstation Player 可讓您在計算機上啟動以前創建的任何虛擬機 - 這使得測試和安裝不同的應用程序變得簡單和安全。 VMware Player 還允許您將虛擬機恢復到之前的狀態,從而防止對您的計算機進行任何不必要的更改。所有使用虛擬機的用戶都知道,他們被存儲在硬盤上,就像可以被各種各樣的 VMware 軟件播放器激活和加載的文件一樣,其中 VMware Player ... VMware Workstation Player 軟體介紹

What's new in this version:

Fixed:
- Move Untracked annotation to task level
- Improve error message when --project-cache-dir is used together with --watch-fs
- Test Suite cannot add version catalog item
- 7.3-rc-1 --project-cache-dir incompatible with org.gradle.vfs.watch=true
- SourceSet with name 'test' not found in KMP
- 7.3-rc-1: Incubating test suite changes breaks existing build
- Fix minor JvmTestSuitePlugin docs formatting issue
- Disable caching and up-to-date checks completely for task
- [Regression] Incremental annotation processor fails with "Attempt to recreate a file for type"
- Regression in Intellij Idea integration for Scala 3
- Support for Scaladoc with Scala 3
- JDK17 + JUnit broken test scanning
- Gradle 7.3 snapshot: dependencies task fails with "Build output cleanup registry has already been finalized - cannot register more outputs"
- Document the danger of publishing a library with a dependency on an enforcedPlatform
- Configuration cache corrupted: NonSerializableMemoizingSupplier, DefaultJvmInstallationMetadata, JavaToolchain
- Implement JvmTestSuite#useTestNG
- Add javadoc for JvmTestSuite#useSpock and #useKotlinTest
- Investigate possible breakage with test suite classpath
- gradle depends on an insecure third-party JAR package that contains the CVE vulnerability
- VFS couldn't add watch, error = 2
- Make DisableCachingByDefault non-incubating
- Update existing test coverage to use new test suite API
- Add documentation to user manual for test suite API
- Support TestNG and Spock as a testing framework options
- Update build init to provide opt-in to best practices based on incubating APIs
- Allow version catalog sub-accessors for platform, enforcedPlatform, test-fixtures and variantOf
- Ignore empty directories on Java sourcepath compile option
- Scala plugin doesn't pick jvm-target from java targetCompatability / toolchain
- Configuration Cache: ClassNotFoundException when reusing cache for java-gradle-plugin project
- In version catalog libs, alias 'jme3-plugins' is not a valid alias — Works in 7.1.1, fails in 7.2
- Add more tests for untracked properties
- Document untracked task properties
- Allow Copy tasks to mark their output as untracked
- Version Catalog: Sub-accessors and alias overload not supported for plugins.
- Cannot import project using Gradle 7.3 snapshot into IntelliJ
- Dependency resolution fails with 'Corrupt serialized resolution result'
- Allow declaring untracked task properties
- Configuration cache issue with :pluginUnderTestMetadata when java-gradle-plugin has project dependency
- Please document Kotlin language compatibility with Gradle Build tool versions.
- Version catalog should allow users to configure libraries with plugin suffix
- Documentation: Incorrect instructions to increase inotify limits
- The exclude won't be able to exclude rewritten dependency
- Make MinimalExternalModuleDependency#toString work
- Provide override for enforcedPlatform(Provider<MinimalExternalModuleDependency>) similar to platform
- Inconsistent task selector behavior in multi-projects build
- Gradle sometimes deadlocks at the start of task execution
- Ensure `JavaToolchain` API compatibility with the configuration cache
- Performance regression for multi-stage incremental annotation processors
- Configuration Cache fails to load after Dynamic Version TTL expires.
- providedRuntime is added to compileClasspath when using the war plugin
- Deprecation Warning Appears after Upgrading to Gradle 7.0
- Support JDK 17
- Support for Scala3
- Configuration cache should capture input normalization
- Endless creation of crashing daemons after upgrading to 6.0.1 or 6.1.1
- Gradle should not add non-existing paths to class paths
- Proper incremental Java/Groovy joint compilation
- ConcurrentModificationException in AbstractStyledTextOutput
- For idea plugin, `.add`ing an excluded folder does not work, only reassignment works
- ScalaDoc for Scala 3 breaks multi-module build
- NullPointerException when building with gradle-7.3-rc2 and java 17

Gradle 7.3 相關參考資料
Gradle 7.3 Release Notes - Gradle User Manual

Upgrade instructions. Switch your build to use Gradle 7.3 by updating your wrapper: ./gradlew wrapper --gradle-version=7.3. See the ...

https://docs.gradle.org

Gradle 7.3-rc-1 Release Notes

The Gradle team is excited to announce Gradle 7.3-rc-1. This release introduces a declarative test suite API for JVM projects, adds ...

https://docs.gradle.org

Gradle 7.3-rc-2 Release Notes

The Gradle team is excited to announce Gradle 7.3-rc-2. This release introduces a declarative test suite API for JVM projects, adds support for building ...

https://docs.gradle.org

Gradle 7.3-rc-3 Release Notes

The Gradle team is excited to announce Gradle 7.3-rc-3. This release introduces a declarative test suite API for JVM projects, adds support for building ...

https://docs.gradle.org

Installation - Gradle

4 天前 — Installing manually. Step 1. Download the latest Gradle distribution. The current Gradle release is version 7.3, released on 09 Nov 2021. The ...

https://gradle.org

Nightly - Gradle

4 天前 — Experience the cutting-edge features of the Gradle build tool by installing Gradle nightly manually or with the Gradle Wrapper.

https://gradle.org

Release Candidate - Gradle

4 天前 — Just switch your build to use Gradle 7.3 RC5 quickly by updating your wrapper properties: ./gradlew wrapper --gradle-version=7.3-rc-5 ...

https://gradle.org

Releases - Gradle

Find binaries and reference documentation for current and past versions of Gradle.

https://gradle.org

Releases · gradlegradle - GitHub

2021年10月12日 — The Gradle team is excited to announce Gradle 7.3. Read the Release Notes. We would like to thank the following community members for their ...

https://github.com