Closed renovate[bot] closed 1 year ago
renovate[bot]
commented
1 year ago Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
codecov[bot]
commented
1 year ago Merging #226 (8391df9) into main (b262e3a) will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## main #226 +/- ##
===========================================
Coverage 100.00% 100.00%
Complexity 2 2
===========================================
Files 1 1
Lines 4 4
===========================================
Hits 4 4 | Flag | Coverage Δ | |
|---|---|---|
| integration-tests | 100.00% <ø> (ø) |
|
| unit-tests | 100.00% <ø> (ø) |
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
This PR contains the following updates:
7.6.1->8.0.24.5.1->5.2.04.5.1->5.2.04.5.1->5.2.05.8.2->5.9.22.17.2->2.20.09.2->10.8.16.5.1->6.16.0Release Notes
gradle/gradle
### [`v8.0.2`](https://togithub.com/gradle/gradle/releases/tag/v8.0.2): 8.0.2 The Gradle team is excited to announce Gradle 8.0.2. This is the second patch release for Gradle 8.0. We recommend using 8.0.2 instead of 8.0. It fixes the following issues: - [#23698](https://togithub.com/gradle/gradle/issues/23698) Gradle 8 RC2 runs out of metaspace - [#23962](https://togithub.com/gradle/gradle/issues/23962) Java/Scala build with no explicit toolchain: build fails with Gradle 8.0.1 / Scala 2.13 - [#23990](https://togithub.com/gradle/gradle/issues/23990) Gradle 8.0.+ silently dropped support for custom compilers in `JavaCompile` - [#24031](https://togithub.com/gradle/gradle/issues/24031) InstrumentingTransformer generates different class files in Gradle 8 and 7.6 which leads to Remote Build-Cache misses - [#24109](https://togithub.com/gradle/gradle/issues/24109) Extending an already resolved configuration no longer works correctly - [#24122](https://togithub.com/gradle/gradle/issues/24122) Update configuration cache state for some plugins - [#24129](https://togithub.com/gradle/gradle/issues/24129) includeBuild in PluginManagementSpec deincubated in Gradle 8, docs still say it's incubating Issues fixed in the first patch release: - [#21551](https://togithub.com/gradle/gradle/issues/21551) Document integration of Scala plugin with toolchains and problems with `target` flag - [#23888](https://togithub.com/gradle/gradle/issues/23888) `--no-rebuild` suddenly gone without new deprecation cycle and without the reason for its undeprecation being void - [#23905](https://togithub.com/gradle/gradle/issues/23905) Gradle 8.0 fails Scala build with isBlank not found in String class error [Read the Release Notes](https://docs.gradle.org/8.0.2/release-notes.html) ##### Upgrade Instructions Switch your build to use Gradle 8.0.2 by updating your wrapper: ./gradlew wrapper --gradle-version=8.0.2 See the [Gradle 7.x upgrade guide](https://docs.gradle.org/8.0.2/userguide/upgrading_version\_7.html#changes\_8.0) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.0.2. ##### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss). ### [`v8.0.1`](https://togithub.com/gradle/gradle/releases/tag/v8.0.1): 8.0.1 This is a patch release for 8.0. We recommend using 8.0.1 instead of 8.0. It fixes the following issues: - [#21551](https://togithub.com/gradle/gradle/issues/21551) - Document integration of Scala plugin with toolchains and problems with `target` flag - [#23888](https://togithub.com/gradle/gradle/issues/23888) - `--no-rebuild` suddenly gone without new deprecation cycle and without the reason for its undeprecation being void - [#23905](https://togithub.com/gradle/gradle/issues/23905) - Gradle 8.0 fails Scala build with isBlank not found in String class error [Read the Release Notes](https://docs.gradle.org/8.0.1/release-notes.html) #### Upgrade Instructions Switch your build to use Gradle 8.0.1 by updating your wrapper: ./gradlew wrapper --gradle-version=8.0.1 See the [Gradle 7.x upgrade guide](https://docs.gradle.org/8.0.1/userguide/upgrading_version\_7.html#changes\_8.0) to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.0.1. #### Reporting Problems If you find a problem with this release, please file a bug on [GitHub Issues](https://togithub.com/gradle/gradle/issues) adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the [forum](https://discuss.gradle.org/c/help-discuss).mockito/mockito
### [`v5.2.0`](https://togithub.com/mockito/mockito/releases/tag/v5.2.0) [Compare Source](https://togithub.com/mockito/mockito/compare/v5.1.1...v5.2.0) *Changelog generated by [Shipkit Changelog Gradle Plugin](https://togithub.com/shipkit/shipkit-changelog)* ##### 5.2.0 - 2023-03-09 - [25 commit(s)](https://togithub.com/mockito/mockito/compare/v5.1.1...v5.2.0) by Andriy Redko, Iulian Dragos, Roberto Trunfio, Róbert Papp, dependabot\[bot], jfrantzius, tobiasbaum - Fixes 2933: IOUtils does not depend on platform encoding any more [(#2935)](https://togithub.com/mockito/mockito/pull/2935) - Execution with mockito-inline fails on platforms with EBCDIC as default encoding [(#2933)](https://togithub.com/mockito/mockito/issues/2933) - Bump io.github.gradle-nexus:publish-plugin from 1.2.0 to 1.3.0 [(#2932)](https://togithub.com/mockito/mockito/pull/2932) - Bump versions.bytebuddy from 1.14.0 to 1.14.1 [(#2931)](https://togithub.com/mockito/mockito/pull/2931) - Bump com.diffplug.spotless from 6.15.0 to 6.16.0 [(#2930)](https://togithub.com/mockito/mockito/pull/2930) - Bump com.google.googlejavaformat:google-java-format from 1.15.0 to 1.16.0 [(#2928)](https://togithub.com/mockito/mockito/pull/2928) - Bump io.github.gradle-nexus:publish-plugin from 1.1.0 to 1.2.0 [(#2924)](https://togithub.com/mockito/mockito/pull/2924) - Feature 2921 generic types [(#2923)](https://togithub.com/mockito/mockito/pull/2923) - Bump com.github.ben-manes.versions from 0.45.0 to 0.46.0 [(#2922)](https://togithub.com/mockito/mockito/pull/2922) - Use generic type information in TypeBasedCandidateFilter to circumvent type erasure [(#2921)](https://togithub.com/mockito/mockito/issues/2921) - Make project relocatable by using relative paths in the OSGi test task [(#2920)](https://togithub.com/mockito/mockito/pull/2920) - Cache misses due to OSGi tests referencing absolute paths [(#2919)](https://togithub.com/mockito/mockito/issues/2919) - Bump versions.bytebuddy from 1.13.0 to 1.14.0 [(#2918)](https://togithub.com/mockito/mockito/pull/2918) - Bump gradle/wrapper-validation-action from 1.0.5 to 1.0.6 [(#2917)](https://togithub.com/mockito/mockito/pull/2917) - Bump com.diffplug.spotless from 6.14.1 to 6.15.0 [(#2913)](https://togithub.com/mockito/mockito/pull/2913) - Bump versions.bytebuddy from 1.12.23 to 1.13.0 [(#2912)](https://togithub.com/mockito/mockito/pull/2912) - Bump ru.vyarus.animalsniffer from 1.6.0 to 1.7.0 [(#2911)](https://togithub.com/mockito/mockito/pull/2911) - Bump org.codehaus.groovy:groovy from 3.0.14 to 3.0.15 [(#2910)](https://togithub.com/mockito/mockito/pull/2910) - Fixes [#2905](https://togithub.com/mockito/mockito/issues/2905) : ThreadLocal classes can be mocked. [(#2908)](https://togithub.com/mockito/mockito/pull/2908) - StackOverflow while mocking a ThreadLocal on Mockito 5.1.1 [(#2905)](https://togithub.com/mockito/mockito/issues/2905) - Fix most Gradle warnings in build [(#2904)](https://togithub.com/mockito/mockito/pull/2904) - Android CI improvements, improves [#2892](https://togithub.com/mockito/mockito/issues/2892) [(#2903)](https://togithub.com/mockito/mockito/pull/2903) - Bump com.diffplug.spotless from 6.14.0 to 6.14.1 [(#2902)](https://togithub.com/mockito/mockito/pull/2902) - Bump versions.bytebuddy from 1.12.22 to 1.12.23 [(#2901)](https://togithub.com/mockito/mockito/pull/2901) - CI on Android API level 33 for Java 11 compatibility testing [(#2899)](https://togithub.com/mockito/mockito/pull/2899) - Bump kotlinVersion from 1.8.0 to 1.8.10 [(#2897)](https://togithub.com/mockito/mockito/pull/2897) - Bump com.github.ben-manes.versions from 0.44.0 to 0.45.0 [(#2895)](https://togithub.com/mockito/mockito/pull/2895) - Simplify and modernize Android Test module. [(#2894)](https://togithub.com/mockito/mockito/pull/2894) - Set up Android Github Action pipeline. Fixes [#2892](https://togithub.com/mockito/mockito/issues/2892) [(#2893)](https://togithub.com/mockito/mockito/pull/2893) ### [`v5.1.1`](https://togithub.com/mockito/mockito/releases/tag/v5.1.1) *Changelog generated by [Shipkit Changelog Gradle Plugin](https://togithub.com/shipkit/shipkit-changelog)* ##### 5.1.1 - 2023-01-30 - [1 commit(s)](https://togithub.com/mockito/mockito/compare/v5.1.0...v5.1.1) by Andriy Redko - StackWalker.Option not found on Mockito 5.1.0 [(#2891)](https://togithub.com/mockito/mockito/pull/2891) - StackWalker.Option not found on Mockito 5.1.0 [(#2890)](https://togithub.com/mockito/mockito/issues/2890) ### [`v5.1.0`](https://togithub.com/mockito/mockito/releases/tag/v5.1.0) *Changelog generated by [Shipkit Changelog Gradle Plugin](https://togithub.com/shipkit/shipkit-changelog)* ##### 5.1.0 - 2023-01-29 - [12 commit(s)](https://togithub.com/mockito/mockito/compare/v5.0.0...v5.1.0) by Andriy Redko, Ashley, Róbert Papp, Stephan Schroevers, Tim te Beek, dependabot\[bot] - Fixes some mistakes and missing details in documentation [(#2889)](https://togithub.com/mockito/mockito/pull/2889) - Bump com.diffplug.spotless from 6.13.0 to 6.14.0 [(#2888)](https://togithub.com/mockito/mockito/pull/2888) - Clean up JDK-8 related code [(#2883)](https://togithub.com/mockito/mockito/pull/2883) - Feat: reified mock overloads [(#2882)](https://togithub.com/mockito/mockito/pull/2882) - Clean up JDK-8 related code [(#2879)](https://togithub.com/mockito/mockito/issues/2879) - Bump assertj-core from 3.24.1 to 3.24.2 [(#2875)](https://togithub.com/mockito/mockito/pull/2875) - Make sure the tests use mock maker with intended member accessor [(#2872)](https://togithub.com/mockito/mockito/pull/2872) - Bump com.diffplug.spotless from 6.12.1 to 6.13.0 [(#2871)](https://togithub.com/mockito/mockito/pull/2871) - Remove broken link from `CONTRIBUTING.md` [(#2870)](https://togithub.com/mockito/mockito/pull/2870) - Update outdated badge 3.x to 5.x [(#2869)](https://togithub.com/mockito/mockito/pull/2869) - Broken link in `CONTRIBUTING.md` [(#2868)](https://togithub.com/mockito/mockito/issues/2868) - Set current version to 5.x in README and highlight changes [(#2867)](https://togithub.com/mockito/mockito/pull/2867) - Annotate `Mockito#{mock,spy}(T... reified)` with `@SafeVarargs` [(#2866)](https://togithub.com/mockito/mockito/pull/2866) - Make sure the tests use mock maker with intended member accessor [(#2855)](https://togithub.com/mockito/mockito/issues/2855) - Improve examples for InOrder [(#2843)](https://togithub.com/mockito/mockito/pull/2843) ### [`v5.0.0`](https://togithub.com/mockito/mockito/releases/tag/v5.0.0) ##### Mockito 5: prepare for future JDK versions For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API. Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker. Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working. ##### Switch the default mockmaker to `mockito-inline` Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle. This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery. As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior. While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes. For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass. Massive thanks to community member [@reta](https://togithub.com/reta) who implemented this change. Note: this does not affect `mockito-android` nor testing on Android. ##### When should I still be using the subclass mockmaker? There are legitimate remaining use cases for the subclass mockmaker. For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice. Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility. Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+. We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker. If you want to use the subclass mockmaker instead, you can use the new `mockito-subclass` artifact (published [on Maven Central](https://search.maven.org/artifact/org.mockito/mockito-subclass) along with all our other artifacts). ##### Update the minimum supported Java version to 11 Mockito 4 supports Java 8 and above. Similar to other open source projects, we are moving away from JDK 8 and to newer versions. The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working. Lately we have been running into more and more JDK 8 breakages. Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes [issues with the `SecurityManager`](https://togithub.com/mockito/mockito/issues/2798). Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well. Massive thanks to community member [@reta](https://togithub.com/reta) who implemented this change. ##### What should I do if I still run JDK 8? For JDK 8 and below, you can keep on using Mockito 4. This is similar to if you are using JDK 6, for which you can keep on using Mockito 2. The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal. However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future. ##### New `type()` method on `ArgumentMatcher` One of our most used public API's for customizing Mockito is the [`ArgumentMatcher` interface](https://javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/ArgumentMatcher.html). The interface allows you to define a custom matcher, which you can pass into method arguments to provide more targeted matches. One major shortcoming of the `ArgumentMatcher` was the lack of varargs support. There were many, many issues filed related to varargs and Mockito unable to handle them. Community member [@big-andy-coates](https://togithub.com/big-andy-coates) put in a lot of effort to come up with an appropriate solution, including fully implementing and comparing 2 approaches. Ultimately, we decided that introducing a new `type()` method on `ArgumentMatcher` is the best solution. As a result, it is now possible to update your custom matchers to implement varargs support, if you so desire. Note that `ArgumentMatcher` is still a `@FunctionalInterface` and can therefore still be written as a lambda. Massive thanks to community member [@big-andy-coates](https://togithub.com/big-andy-coates) who implemented this change. ##### What is the effect of this new method? For varargs methods, there was previously a way to only match zero arguments, or two or more arguments, by using the exact number of matchers, i.e. ```java long call(String... args); // Will match calls with exactly zero arguments: when(mock.call()).thenReturn(0L); // Will match calls with exactly two arguments: when(mock.call(any(), any())).thenReturn(0L); ``` But following the pattern to match exactly one argument: ```java when(mock.call(any())).thenReturn(0L); ``` doesn't work, as `any` is "vararg aware", so Mockito matched the `any` against *each element* of the varargs parameter, meaning it will match any number of arguments, i.e. the above would of matched all of these: ```java mock.call(); mock.call("a"); mock.call("a", "b"); ``` With the new `type` method, it's now possible to differentiate matching calls with any exact number of arguments, or to match any number of arguments. ```java // Match any number of arguments: when(mock.call(any(String[].class))).thenReturn(1L); // Match invocations with no arguments: when(mock.call()).thenReturn(1L); // Match invocations with exactly one argument: when(mock.call(any())).thenReturn(1L); // Alternative to match invocations with exactly one argument: when(mock.call(any(String.class))).thenReturn(1L); // Match invocations with exactly two arguments: when(mock.call(any(), any())).thenReturn(1L); ``` Therefore, if you want to match 0 or more arguments, use `any(String[].class)`. If you want to match an exact number of arguments, use `any(String.class)` (and specify as many `any` matchers as arguments you want to match on). In a similar fashion, the behavior of `ArgumentCaptor.forClass` has changed as well. If you want to capture all arguments, use an `ArgumentCaptor` for `String[]`, otherwise `String`: ```java // Will capture 1 string @Captor private ArgumentCaptorapache/logging-log4j2
### [`v2.19.0`](https://togithub.com/apache/logging-log4j2/blob/HEAD/CHANGELOG.adoc#If-srcchangelogreleaseVersion-directory-eg-srcchangelog2190-already-exists-with-certain-content-changelog-releaser-profile-will-only-move-new-changelog-entry-files-and-override-releasexml-changelogadocftl-will-not-be-touched-if-it-already-exists) # This allows one to run `changelog-releaser` profile multiple times, e.g., to incorporate changes added to a release candidate. . Edit the populated `.changelog.adoc.ftl` . `git add` the changes in `src/changelog` and commit themcheckstyle/checkstyle
### [`v10.8.1`](https://togithub.com/checkstyle/checkstyle/releases/tag/checkstyle-10.8.1) [Compare Source](https://togithub.com/checkstyle/checkstyle/compare/checkstyle-10.8.0...checkstyle-10.8.1) Checkstyle 10.8.1 - https://checkstyle.org/releasenotes.html#Release\_10.8.1 Bug fixes: [#4930](https://togithub.com/checkstyle/checkstyle/issues/4930) - LocalizedMessage should use ModuleName in compareTo methodOther Changes:
Fix 'set-milestone-on-referenced-issue'
Specify violation messages in input files
Update documentation for AnnotationUseStyle
Execute upload of -all jar separately
Switch to PAT secret in set-milestone workflow
Remove execution of upload -all jar from new-milestone-and-issue-in-other-repo
Update Tests to use new 'verifyXxxxxx' method or 'execute' that use inlined config in Input files
Add forgotten secret inherit in release
Create GitHub action to put current milestone on issue of closed PR
Use dynamic names for release workflow runs
Make action to trigger all release steps
CommitValidationTest fails on revert commits
Keep workflow input descriptions consistent
Other Changes:
Specify violation messages in input files.
Make action to trigger all release steps
Make scripts and configurations filenames consistent
CommitValidationTest should ignore the release process
Use Shellcheck to resolve violations code in Shell Script
Update doc for JavadocType
Release perform action is failing
Replace all usages of xmlstarlet with getCheckstylePomVersion from util.sh
confg: cancel 10.8.0 release, see details in #12762
End of free builds for CloudBees CodeShip
Define variable for non-main-files-suppressions file
Fix RegexpOnFileNameCheck message keys
pitest: groovy does not run when profile fails
Resolve surviving annotation mutations for pitest
Checker: false violation removals on other failures
Validation for next version in GitHub action
pitest-survival-check-xml.groovy: prints nothing when there are no differences
`pitest-survival-check-xml.groovy` should automatically update list of suppressions
Remove admins from white list on commit validation
Github action "Release perform"
pitest: validate wildcards on target classes
Issue 12705: remove .m2 for codenarc execution to make it more stable on download
Github action to copy to sourceforge does not work
update all release action to have 'Setup local maven cache' step to optimize download of artifacts
Push 'all' jar action is not working and not failing execution
Other Changes:
action 'R: Close/Create Milestone' is not working
Resolve surviving pitest-design-check mutations for pitest
Resolve surviving pitest-coding-require-this-check mutations for pitest
linkcheck report full of error on damaged links to javadoc
Resolve violation from ResultOfMethodCallIgnored inspection
All Github CI workflows should have concurrency of 1
Picocli's coloring interfering with tests
Remove Apex project from usage in testing
Resolve surviving pitest-metrics-check mutations for pitest
Update Tests to use new 'verifyXxxxxx' method or 'execute' that use inlined config in Input files
Resolve Pitest for profile coding-2
Resolve surviving pitest-blocks mutations for pitest
doc: explanation on versioning of checkstyle
Corrects classes scanned for pitest to include sub-classes
Resolve surviving pitest-whitespace mutations for pitest
Resolve surviving sizes mutations for pitest
Empty ErrorStream in `checker-framework.groovy` to prevent buffer exhaustion and external processes from blocking
Resolve surviving pitest-java-ast-visitor mutations for pitest
Specify violation messages in input files.
Resolve surviving modifier mutations for pitest
Resolve surviving naming mutations for pitest
Restore pitest.sh to ease operation on local
Lint GitHub Actions workflows executed twice
`bump_license_year.yml` not adding year to commit message.
Other Changes:
Resolve pitest for profile metrics
Review usages of `BeforeAll` in tests
Create CI task to lint github actions
Run regression testing in CI over openjdk19
Replace backward slash with forward slash while creating `CheckerFrameworkError` object in `checker-framework.groovy`
Convert sevntu-checkstyle-check to ant run
doc: remove 'pre' tags from description
Create YAML linting CI task
Use Shellcheck to resolve violations code in Shell Script
All scripts that print example of execution should not have hardcoded name in message
'R: Push Release Notes' makes xml section version as snapshot
'R: Push Release Notes' failing on push
Remove 'releasenotes.xml after commit:'
'R: Push Release Notes' failing
Create CI task to enforce '.ci' directory contains only script files
Other Changes:
doc: releasenotes 10.5.0
Resolve Pitest suppression for RightCurlyCheck
Remove new curl parameter from all GitHub actions for release
Update Tests to use new 'verifyXxxxxx' method or 'execute' that use inlined config in Input files
Github action "Copy site to sourceforge"
Issue #11604: separates detail ast from xpath
PMD warning in execution logs
failure of update github.io to clone checkstyle.github.io
Enforce file size on Java inputs
failure to publish github release notes ' R: Publish GitHub Page'
Resolve Pitest suppression for AccessModifierOption
Resolve Pitest suppression for SeparatorWrapCheck
Re-enable sonar
Investigate why GITHUB token has no access to issues
Update doc for MutableException
Update Test Configuration To Support Adding TreeWalker Property
Missing Link found on Checkstyle docs
doc: archive release notes for 8.0-8.34
add release number validation
Create instance of regexp check to enforce usage of 'fail-with-body' in curl commands
Action 'Bump version/Update Milestone' is failing to update milestones
Specify violation messages in input files.
'R: Publish GitHub Page' failing at perform curl command but action status is succcess
Debug documentation is not clear
Improper text in NewLineAtEndOfFileCheck documentation
doc: expanded documentation on severities
Resolve Pitest for Block Profile-2
Other Changes:
Overview Section is quite confusing
Move codenarc to non GitHub CI
CI: validate PR number when commit is for PR
Create CI task to fail PR if merge commit exists
checker-framework.groovy depends too much on name of repo
Resolve Switch case mutation for ParenPad
Rename all 'Checker-Framework / checker-..' actions
Resolve Pitest suppression for ParenPad
Resolve Pitest suppression for Javadoc profile
Resolve Pitest suppression for misc profile
dependency: bump mockito-inline from 4.8.0 to 4.8.1
UnusedImports doc: add limitation regarding same-name imports
Update doc for EmptyLineSeparator
Update verify-no-exception-configs validation
Pitest/Checker: Drop New/Unnecessary Displays And Switch to Git Diff
Add example of custom jars to Ant Documentation
Resolve Pitest suppression for block profile
Resolve Pitest suppression for EmptyForInitializerPad-2
doc: Update SuppressionXpathSingleFilter example (related to #3095)
doc: remove teamcity badge but keep links in case we will restore it
Create IDEA Inspections Docker image for CircleCI
Specify violation messages in input files.
Resolve Pitest suppression for SeperatorWrapCheck
Resolve Pitest suppression for EmptyForInitializerPadCheck
Resolve Pitest suppression for MethodParamPadCheck
Resolve Pitest suppression for OperatorWrapCheck
Resolve Pitest suppression for AbstractParenPadCheck - 2
Resolve Pitest suppression for EmptyForIteratorPadCheck
Resolve Pitest suppression for AbstractParenPadCheck
Remove changes needed for PMD Accessor violations from Java 11 improvements
Minor word missing in checkstyle docs
doc: fix formatting mistake
Other Changes:
Update releasenotes to use GitHub Pages execution
Allow SuppressWarningHolder to suppress the violation with NameCheck
Pitest: Kill all surviving mutations
Pitest: Activate "ALL" mutator group
Use Shellcheck to resolve violations code in Shell Script
pitest: increase mutation coverage for pitest-imports profile to 100%
Update GitHub Action for bump-license-year.sh
Solve fb-contrib errors
Remove pitest mutation checking HTML model
automate execution by Github action bump-license-year.sh on first day of month
update code base to have javadoc tag to explain noinspection tag content
doc: put example of enableExternalDtdLoad to xdoc
update doc for SuppressWarningsHolder
releasenotes script generated empty commit
Include CDG Accelerator Plugin to boost pitest performance
Enforce file size on Java inputs
Expand XPath IT Regression Testing
There are semantic problems in the Chinese error message of keyword `design.forExtension` .
prepare-settings.sh fails to create settings.xml
Use groovy version provided by `apt` in pitest.yml
tweet-releasenotes.sh does not check env variables
download of m2 cache from sourceforge.io is slow
infra: turns off create dependency reduced pom for shade plugin
Update Tests to use new 'verifyXxxxxx' method or 'execute' that use inlined config in Input files
Specify violation messages in input files.
pitest: increase mutation coverage for javadoc profile to 100%
Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.