内容简介:30 issues have been fixed in Gradle 5.1.Previously, only exclude rules directly declared on published configurations (e.g.Features that have become superseded or irrelevant due to the natural evolution of Gradle become
Gradle 5.1 已发布,更新内容如下
Fixed issues
30 issues have been fixed in Gradle 5.1.
-
[ #7961 ] - Gradle 5 fails for manually added ListProperty
-
[ #7950 ] - Scheduled artifact transform fails with "Transformation hasn't been executed yet"
-
[ #7878 ] - TestNG parallel test execution via Gradle fails with "Received a completed event for test with unknown id".
-
[ #7873 ] - Implement fallback mechanism for updating file modification timestamp
-
[ #7858 ] - Document repository content filtering
-
[ #7766 ] - Improve prodived context for artifact transforms
-
[ #7729 ] - Fix deprecation warning when exposing dependencies to artifact transforms
-
[ #7648 ] - Investigate providing context to transforms
-
[ #7617 ] - Incorrect stderr redirection in Tooling API
-
[ #7570 ] - Up-to-date checks for ArtifactTransforms
-
[ #7564 ] - CONSTANT_TIME_FOR_TAR_ENTRIES = 0 causes issues with Java applications
-
[ #7511 ] - Failure in included build's `BuildListener.buildFinished()` listener prevents build scan publication
-
[ #7502 ] - Play 2.4 route compilation errors were silently ignored
-
[ #7485 ] - No value `ListProperty` and `SetProperty` shouldn't allow adding elements
-
[ #7381 ] - Improved declared inputs and outputs for `Sign` task
-
[ #7061 ] - Gradle should always respect the extra attributes when selecting artifacts transforms chains
-
[ #6876 ] - Option can not be applied to Property<String>
-
[ #6863 ] - Add MapProperty type to support lazy configuration of key/value types
-
[ #6766 ] - Inherited configuration exclusions are not published to the POM
-
[ #6718 ] - Artifact transform - prefer suffix chains if they exist
-
[ #6632 ] - Only produce new gradle-wrapper.jar when classes changed
-
[ #6453 ] - Junit 5 parallel test execution via Gradle fails with "Received a completed event for test with unknown id".
-
[ #6334 ] - 4.10 rc1 still outputs quite a bit of transform logs
-
[ #5704 ] - Provide a way to define default values for task properties
-
[ #5664 ] - Public comments for new Task API for configuration time avoidance
-
[ #2528 ] - Support composite builds for `plugins` block
-
[ #1369 ] - Allow matching repositories to dependencies
-
[ #8078 ] - wrapper task fails when the version 5.1 is specified.
-
[ #8077 ] - Gradle 5.1 incompatible change in behaviour of task inputs.files.asFileTree.matching -it doesn't filter
-
[ #8074 ] - Spotbugs plugin compatibility with Gradle 5.1 is fixed
Inherited configuration-wide dependency excludes are now published
Previously, only exclude rules directly declared on published configurations (e.g. apiElements
and runtimeElements
for the java
component defined by the Java Library Plugin
) were published in the Ivy descriptor and POM when using the Ivy Publish Plugin
or Maven Publish Plugins
, respectively. Now, inherited exclude rules defined on extended configurations (e.g. api
for Java libraries) are also taken into account.
Deprecations
Features that have become superseded or irrelevant due to the natural evolution of Gradle become deprecated , and scheduled to be removed in the next major Gradle version. See the User guide section on the “ Feature Lifecycle ” for more information.
The following are the newly deprecated items in this Gradle release. If you have concerns about a deprecation, please raise it via the Gradle Forums .
Setters for classes
and classpath
on ValidateTaskProperties
There should not be setters for lazy properties like ConfigurableFileCollection
s. Use setFrom
instead.
validateTaskProperties.getClasses().setFrom(fileCollection) validateTaskProperties.getClasspath().setFrom(fileCollection)
Potential breaking changes
See the Gradle 5.x upgrade guide to learn about breaking changes and considerations when upgrading to Gradle 5.1.
External contributions
We would like to thank the following community members for making contributions to this release of Gradle.
-
Mike Kobit - Add missing
@Deprecatedannotations toProjectLayoutmethods ( gradle/gradle#7344 ) -
Kent Fletcher - Convert
WindowsResourceCompileto use Provider API ( gradle/gradle#7432 ) -
Niklas Grebe - Add more examples of dynamic versions to documentation ( gradle/gradle#7417 )
-
Jonathan Leitschuh - Add Provider API types to
AbstractArchiveTasktask types ( gradle/gradle#7435 ) -
Sebastian Schuberth - Improve init-command comments for Kotlin projects ( gradle/gradle#7592 )
-
Sebastian Schuberth - BuildScriptBuilder: Do not print a trailing space for empty header lines ( gradle/gradle#7887 )
-
Dan Sănduleac - Don't share dependency resolution listeners list when copying configuration ( gradle/gradle#6996 )
-
Olivier Voortman - Do not use a timestamp of 0 for tar file entries ( gradle/gradle#7577 ).
-
John Bennewitz - Allow C++ binary to relocate on Linux ( gradle/gradle#6176 )
-
Alex Saveau - Add option to display tasks from a specific group only ( gradle/gradle#7788 )
-
Till Krullmann - Add
MapProperty( gradle/gradle#6863 ) -
TO XZ - Gradle should always respect the extra attributes when selecting artifacts transforms chains ( gradle/gradle#7061 )
以上就是本文的全部内容,希望本文的内容对大家的学习或者工作能带来一定的帮助,也希望大家多多支持 码农网
本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
处理器虚拟化技术
邓志 / 电子工业出版社 / 2014-5-1 / CNY 109.00
《处理器虚拟化技术》针对在Intel处理器端的虚拟化技术(Intel Virtualization Technology for x86,即Intel VT-x)进行全面讲解。在Intel VT-x技术下实现了VMX(Virtual-Machine Extensions,虚拟机扩展)架构平台来支持对处理器的虚拟化管理。因此,VMX架构是Intel VT-x技术的核心。《处理器虚拟化技术》内容围绕V......一起来看看 《处理器虚拟化技术》 这本书的介绍吧!