Blisk

最新版本 Gradle 8.5

Gradle 8.5

Gradle 8.5
Blisk 是一個基於鉻的瀏覽器,用於 web 開發的基本工具。將其用於同時構建和測試您的網站的桌面和移動版本。 Blisk 使開發人員能夠同時在多個設備上編碼,預覽其更改!

4 使用原因 Blisk:

TIME SAVING
以光速發展!現在您不需要一直刷新頁面,搜索並滾動到所需的元素。 Blisk 從根本上節省了開發和測試的時間。瀏覽器將使你的生產力達到 200%。所以你可以把你的工作快兩倍,把時間花在那些對你真正重要的事情上。或者有一杯咖啡,放鬆.

CODE GURU
Code 像一個超級開發商。 Blisk 瀏覽器使編寫跨設備兼容代碼和監視代碼中的錯誤。因此,您的代碼將適用於任何設備,並且無處不在.

BEST 實踐
使用測試驅動開發等最佳實踐。隨著 Blisk 您的工作流程可以專注於編寫高品質的代碼沒有隱藏的錯誤。您可以同時開發和測試.

ScreenShot

軟體資訊
檔案版本 Gradle 8.5

檔案名稱 gradle-8.5-all.zip
檔案大小
系統 Windows 7 64 / Windows 8 64 / Windows 10 64
軟體類型 免費軟體
作者 Blisk Team
官網 https://blisk.io/
更新日期 2023-11-29
更新日誌

What's new in this version:

Fixed:
- Clean up categories reported via Problems API
- Bug in Tutorial Apply Plugin section
- Rename `Problems#createProblem` to `Problems#create`
- Rename Problem.getWhere() to Problem.getLocations()
- Expand list of file extensions used by cpp-library public headers
- Add Maven test fixture to test POMs generated by Gradle
- Update verfication-metadata to 1.3
- Broken link in "Declaring Repositories" page
- Published source tarballs expect a git repository to build
- In Gradle 8.4, Project.getConfigurations() is marked unstable again
- Generation of Kotlin extensions of the Gradle API is not reproducible
- Upgrade embedded Kotlin to 1.9.20 when available
- unable to create task based on code in documentation
- Wrong Windows instruction
- Pull out test suites to its own project
- Add Version to Version Catalog Javadoc
- Add location information to problem reports for version catalog problems
- The -all distribution is missing the resource files from the src folder
- Usage of GRADLE_HOME for ephemeral builds is wrong
- Problems-api subproject should be java 6 compatible
- Drop :wrapper-shared dependency in :build-cache-packaging
- Wrapper project should output final gradle-wrapper.jar to libs folder
- Let generated Kotlin extensions for the Gradle API be included in the binary compatibility check
- Ensure that the internal problems API can be used in TAPI model builders
- Make IDEA Gradle plugin Isolated Projects compatible
- 8.4 KotlinDsl: ConfigurationContainerScope.detachedConfiguration allows nullable Dependency but will throw NPE
- 8.4 - New configuration shortcut: DependencyScopeConfiguration.invoke isn't available
- add --java-version parameter to gradle init task
- Set visible=false on consumable Configurations
- Binary changes are sometimes not auto-accepted for upgraded properties
- Implement basic location types
- Ignore help task execution request during model building
- Ship the Gradle API Kotlin DSL Extensions JAR within the Gradle distribution
- Add more NowInAndroid based performance tests
- NowInAndroid project is not building with current `master` branch
- Anticipating named Configurations with different allowed usages can cause unexpected behaviors
- Ear Plugin: XML Schema / xmlns in Ear Descriptor for Java EE 8, Jakarta EE 9 and Jakarta EE 10 is missing / invalid
- Hashing a file with upgraded properties fails due to incorrect hashing
- Don't share stateful codecs
- TestLauncher should be able to support test debugging while reusing CC cache entry
- Don't invalidate the cache upon Kotlin DSL `cid` project property changes
- Configuration cache fails when using filtered FileCollection
- Dependency configuration testRuntime still exists in docs
- Reduce log level of directory watcher
- `getDependenciesForVariant` produces duplicate results when a dependency is reachable through two paths
- Tests in gradle/gradle build should not make use of the Foojay Toolchains Plugin
- Clean up next gen build cache prototype
- Move ConsistentResolution code into JavaComponent
- Gradle doesn't expose a comparison failure in test exception causes
- Automatically accept binary changes for Upgraded properties
- Error message when attempting to create a configuration that already exists is confusing
- Continuous Build - changes to task inputs, or changes to input files?
- Gradle not noticing file changes when source files is behind symlink on macOS
- Clarify what "Gradle installation directory" means for `gradlew`
- Generate list of upgraded properties during build
- Provide better diagnostics for the "Unable to delete directory... Failed to delete some children..." error
- Improve error message if value derived from property that does not provide any value
- Clean up internal flags for persistent Java compiler daemon
- Use GroovyCoverage/CheckstyleCoverage/etc pattern for ScalaCoverage
- MavenPublicationErrorChecker can have a more helpful error message
- org.gradle.api.tasks.WriteProperties.setOutputFile deprecated but no suggested alternative
- Support running with Java 21
- Warn if project in settings.gradle has a non existent project directory
- `compileKotlin` task of build with `kotlin-dsl` applied emits warnings when configuration-cache is enabled
- Unpublish :wrapper-shared for Maven
- Make Java plugin compatible with Project Isolation
- Some implicit imports for .gradle.kts are package private
- Alert Plugins of Special Case Exceptions Suppressing Deprecation Warnings
- Update gradle init to provide an option create and use a version catalog
- Document GRADLE_LIBS_REPO_OVERRIDE
- Project isolation: class not found exception if a model is queried twice
- Have a public API to tell if project isolation is enabled.
- Investigate implications of using DefaultJvmVariantBuilder in component-centric model.
- Confusing Licensing Information in Gradle User Manual
- ResolvedArtifact returns incorrect extension for certain artifacts
- Nag for deprecation of BasePluginExtension members
- `VersionCatalogExtension` not added to the `gradle-kotlin-dsl-accessors` during `generatePrecompiledScriptPluginAccessors`
- Add deprecation logging to org.gradle.util.VersionNumber
- Add an option to only generate plaintext and not binary for `--export-keys`
- Corrupt plugin jars end up in Gradle's local caches
- Use the same case for dependency verification metadata and keyring
- Outgoing artifacts as provider of a task output cause the failure
- Resolve dependencies around ValidationProblemId enum
- Wrong licensing legal advice in application plugin documentation?
- Dependency verification's trusted keys is case sensitive
- Settings scripts and plugins should provide APIs to create RegularFile and Directory instances according to the settings layout
- Please include LICENSE in gradle-wrapper.jar
- There should be a public API for creating CopySpec instances at execution time
- DirectoryProperty cannot be used with @Option, throws an obscure exception
-Sync task doesn't handle "." as an "into" subpath correctly
- FileComparisonTestAssertionFailure don't represent AssertionFailueError with one FileInfo
- Duplicated BOM imports in generated POMs
- `CalculateTaskGraphBuildOperationType` build operation should be consistent between `store` and `load` builds

Gradle 8.5 相關參考資料
8.5

沒有這個頁面的資訊。

https://docs.gradle.org

Gradle 8.5 Release Notes

New features and usability improvements · Full Java 21 support · Kotlin DSL improvements · Error and warning reporting improvements · Build init improvements.

https://docs.gradle.org

Gradle 8.5-rc-1 Release Notes

New features and usability improvements · Full Java 21 support · Kotlin DSL improvements · Error and warning reporting improvements · Build init improvements.

https://docs.gradle.org

Gradle 8.5-rc-2 Release Notes

New features and usability improvements · Full Java 21 support · Kotlin DSL improvements · Error and warning reporting improvements · Build init improvements.

https://docs.gradle.org

Gradle 8.5-rc-3 Release Notes

New features and usability improvements · Full Java 21 support · Kotlin DSL improvements · Error and warning reporting improvements · Build init improvements.

https://docs.gradle.org

Gradle 8.5-rc-4 Release Notes

The Gradle team is excited to announce Gradle 8.5-rc-4. Gradle now supports running on Java 21. This release features Kotlin DSL improvements, ...

https://docs.gradle.org

Gradle | Releases

Here you can find binaries and reference documentation for current and past versions of Gradle. You can find the next release candidate or a bleeding edge ...

https://gradle.org

Releases · gradlegradle

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

https://github.com

Starting from which version does Gradle support Java 21?

2023年9月20日 — For full Java 21 support, you can use Gradle 8.5. The release notes say: With this release, Gradle now fully supports compiling, testing and ...

https://stackoverflow.com

Upgrading your build from Gradle 8.x to the latest

Upgrading from 8.5 and earlier. Potential breaking changes. Upgrade to JaCoCo 0.8.11. JaCoCo has been updated to 0.8.11. DependencyAdder renamed to ...

https://docs.gradle.org