Update plugins and dependencies, migrate to JUnit5 and fix issues #164
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some weeks ago the branch release/1.5.x has been added. This pull request includes the changes made there. In addition, it updates plugins and dependencies to the most recent versions, it migrates from JUnit4 to JUnit5, and it fixes various issues.
First, the Maven project has been renewed by using a XSLT transformation (RenewPOM.xslt).
A side effect of updating plugins and dependencies is that the Java sources get reformatted by applying the profile "format".
Various compilation warnings have been fixed, some have been suppressed.
After optimizing imports various issues remain. Find inspection reports before and after fixing them attached (InspectionReports.ante.zip and InspectionReports.post.zip).
After each patch, a complete maven build cycle has been performed. Find log files attached (CompilationLogs.zip). All tests (incl. integration tests) succeed.