DesktopOK (64-bit) 歷史版本列表
更新時間：2020-06-04
更新細節：
更新時間：2020-06-03
更新細節：
更新時間：2020-06-03
更新細節：
What's new in this version:
Fixed:
- Core alignment resolution results keep changing
- Gradle 6.5-milestone-2: build crashes while generating a jar file
- Usage of project.fileTree for dependencies can lead to ordering issues
- Watching on Linux fails with `Received event for unknown watch descriptor 527`
- Amend version sorting to resolve differences on well known qualifiers
- The cache key for @CacheableRule is problematic when dependencies have no metadata
- failOnNonReproducibleResolution() crashes build
- Instant execution fails to serialize a property with finalize on read enabled and whose value is a mapped task output
- java.lang.ClassCastException when compiling groovy gradle source
- Binary store exception
- A "by ancestor" selection reason shows as "Unknown" in dependencyInsight output
- [scala] When the user specifies a non-default version of Zinc, compiler-bridge.jar from DEFAULT_ZINC_VERSION is still used
- Gradle dependency locking > inconsistent dependencies resolution with/without --write-locks option
- Resolving a dependency prevents its further use as a BOM
- ResolvedDependencyResult.getResolvedVariant() can return a null value
- Cannot delete project directory on Windows when watching the file system is enabled
- Slow Scala compilation times in 6.2.2 compared to 5.6.2
- Add a command-line flag to enable watching the file system for changes
- Test if VFS retention works when removing build directory manually
- Document watching the file system
- Support symlinks with VFS retention
- Bad performance when file trees are used as task outputs
- Add Generated annotation to kotlin-dsl generated files
- Add `stopDaemons()` to `GradleConnector` interface
- Provide a way to stop daemon via tooling api
更新時間：2020-05-25
更新細節：
What's new in this version:
- Allow installation when %AppData% is redirected to another location
更新時間：2020-05-24
更新細節：
What's new in this version:
Fixes:
- IMAP stability improvements
- HTML tags in IRC topic changes were rendered incorrectly
- MailExtensions: Websockets could not be used
更新時間：2020-05-23
更新細節：
更新時間：2020-05-22
更新細節：
What's new in this version:
Enhancements:
- Enhanced Sequence view so that when two panels of sequence are visible in a split window, the minimap at the top shows the visible regions from both panels
- Enhanced cloning dialogs to fit on smaller displays
- Support polyA_site point features
- Made various textual enhancements
Fixes:
- Enhanced the GFF3 importer to handle files that mark a single sequence with multiple references
- Fixed an issue that prevented opening of some Vector NTI® .apr alignment files
- Corrected a regression that prevented files in a collection's "Working Set" from being listed in source menus in action dialogs
- Improved stability when importing protein features from another SnapGene file
- Corrected an issue that could result in poor alignments
- Corrected a regression that prevented restriction sites blocked by methylation from being shown in gray in Enzymes View using Numbers mode
- Corrected a regression that prevented sorting of restriction sites in Enzymes view by location of the first site or by distance from the selection
- Ensured proper import of SnapGene online sequence files that contain "&" in their names, such as the COVID-19 genome file
- Corrected a regression that could prevent enzymes in aligned sequences from reflecting the chosen option for displaying enzymes
- Ensured that Enzymes view does not scroll when toggling enzyme visibility
- Corrected an issue that made it difficult to trim aligned sequences by dragging a trimming handle when using double-stranded DNA format
- Improved the export to GenBank and other text formats of features that contain "&" and other symbols in qualifiers
- Improved the appearance of a selection in an aligned sequence when manual trimming partially occludes the selection
- Corrected a regression that prevented invoking the Destroy Restriction Site or Remove Restriction Fragment dialogs by pressing Delete or Backspace in Enzymes view
- Ensured that toggling enzyme visibility no longer marks a file as unsaved
- Fixed an issue that could prevent dashes within gaps from being shown when viewing an alignment to a reference DNA sequence
- Prevented aligned bases from being shown in red at the endpoints of an alignment
- Fixed an issue that could cause "Redo Alignment" to fail for some files
- Ensured that the Edit Feature dialog correctly indicates that segment ranges can overlap if features with overlapping segments were imported from GenBank or other file formats
- Improved the default ratio between the two panel heights when generating a split window
- Prevented unnecessary vertical space from being allocated when laying out aligned sequences in double-stranded DNA format when enzymes are visible
- Improved the file information shown for registered file types in the Windows Explorer and the macOS Finder
- Improved the display of aligned regions in Map view
更新時間：2020-05-20
更新細節：
What's new in this version:
- Windows Terminal now ships with Cascadia Code 2005.15
- All emoji are now sized as recommended by Unicode 13.0. You will see some emoji that are smaller than you want them to be. That's just a fact of life
- Documentation for Windows Terminal has moved to docs.microsoft.com
- Existing user documentation in this repository will be moving to a nice farm upstate in short order
It will not escape your notice that there are two packages in this release:
- WindowsTerminal is the stable build of Terminal
- WindowsTerminalPreview is the preview version, which can be installed side-by-side with the stable version
更新時間：2020-05-18
更新細節：
更新時間：2020-05-16
更新細節：
What's new in this version:
Building, testing and running Java Modules:
- With this release, Gradle supports the Java Module System with everything you need to compile and execute tests for Java modules. You can also build Javadoc and run applications
- While there is some overlap with Gradle's dependency management features, Java Modules offer additional features like module boundaries that are enforced by the Java runtime
The only thing you need to configure is module path inference for the Java plugins:
- java {
- modularity.inferModulePath.set(true)
- Then you just need to make sure that you write a proper Java module by providing a module-info.java descriptor as part of your sources:
- src
- +-- main
- +-- java
- +-- module-info.java
- For more details, head over to the documentation on building modules, building modular applications and testing modules.
- Also feel free to explore the samples
Precompiled Groovy DSL script plugins:
- Script plugins are a convenient way to split up and organize a long build script, but they have some limitations and quirks. Kotlin DSL introduced precompiled script plugins that look like regular build scripts but have all of the advantages of binary plugins. They can:
- be published to a private repository or the Plugin Portal,
- be tested using TestKit,
- be applied using the plugins {} block,
- use the plugins {} block to apply other plugins
- Gradle now allows precompiled script plugins to be written using the Groovy DSL in addition to the Kotlin DSL
- For example, a Gradle script in buildSrc/src/main/groovy/my-plugin.gradle can be used as a plugin in the main project as plugins { id 'my-plugin' }
- Precompiled script plugins are covered in more depth in the user manual. There is also a sample available that demonstrates the feature in action
Single dependency lock file per project:
- Dependency locking is a mechanism for creating reproducible builds even when using dynamic dependency versions. This release adds an improved dependency locking file format that results in fewer lock files in most projects that use this feature. In addition, when using this format, the lock file name and location can be configured
- This format will become the default lock file format in Gradle 7.0. For now, it is required to opt-in to use it
- Take a look at the documentation for more information and how to enable the feature
Better dependency variant matching error messages:
- Gradle provides a powerful variant-aware dependency management engine
- This release introduces clearer variant matching error messages for the JVM ecosystem
- In previous releases, these error messages could be difficult to understand and sometimes lacked enough context to figure out what to do. Gradle 6.4 improves these error messages by making them more human-readable and introducing colors to the console to highlight problems.
Improvements to PMD code quality plugin:
- Incremental analysis is enabled by default
- As of Gradle 6.4, the PMD plugin uses incremental analysis by default. This can significantly reduce analysis time on subsequent builds.
- For builds relying on a version of PMD older than 6.0.0, you will need to explicitly disable incremental analysis.
- Specify number of violations required before the build fails
- The PMD plugin now lets you set the number of violations before the build fails. This can make it easier to introduce PMD into existing projects that may initially have many violations.
- If you wanted to fail the build if the number of violations is above 150, you can set maxFailures to 150.
- pmd {
- maxFailures = 150
- This was contributed by Matthew Duggan.
- Security warning about using DEBUG level logging
- Potentially sensitive information is logged when Gradle is executed with debug level logging, such as sensitive credentials, authentication tokens or internal repository URLs. Much of this logging occurs deep in components of the JVM and other libraries outside the control of Gradle. While debugging, this information may be inherently useful. However, this information can be unintentionally exposed when Gradle builds are executed on Continuous Integration services where build logs are publicly-accessible. See the recent update about the fixed Plugin Portal vulnerability for an example of this security risk.
- Gradle now warns users about the risks of using DEBUG level logging.
- We recommend plugin maintainers avoid logging sensitive information if possible, and if it's not possible, that all sensitive information be logged exclusively at the DEBUG log level.
Fixed issues:
2 issues have been fixed in Gradle 6.4.1.
[#13069] - Regression: Different daemons are used between IDE and CLI builds for the same project
[#13057] - Regression: Main-Class attribute always added to jar manifest when using application plugin