Gradle 6.1.1 軟體資訊介紹&下載

Adobe DNG Converter,軟體教學,軟體下載,電腦問題,電腦教學
Adobe DNG Converter 是一個免費的實用程序,可以將 600 多個攝像機的文件轉換為 DNG 格式,使您能夠輕鬆將相機專用的原始文件轉換為更通用的 DNG 原始文件.

Digital Negative 的開發旨在解決缺乏專有和開放的標準每個數碼相機創建的獨特的原始文件。 DNG 允許攝影師將其原始相機文件歸檔為單一格式,便於將來進行編目和訪問。隨著格式規範免費提供,任何開發人員都可以構建支持和利用 DNG 的軟件。欲了解更多信息,請訪問數字負片頁面。

添加了以下相機的支持。訪問 Camera Raw 頁面以獲取支持的攝像機的完整列表.

Adobe DNG Converter Screenshot 1
Adobe DNG Converter Screenshot 2

Gradle 6.1.1

Windows 7 / Windows 7 64 / Windows 8 / Windows 8 64 / Windows 10 / Windows 10 64


Adobe Systems Inc


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
- Please see the user manual for more details
- 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
- Fixed issues

4 issues have been fixed in Gradle 6.1.1:
- Gradle 6.1 generates an empty .gradle and gradle directories on each execution in subproject directories
- Memory regression when resolving large artifacts while computing checksums
- Missing fixed issues from Gradle 6.1 release notes
- Plugins using kotlin-dsl and compiled with 6.1 are incompatible with Gradle 6.0

Adobe DNG Converter 相關參考資料