Migrate AsciidoctorDoxiaParserTest from Groovy to Java #519
Conversation
This file contains 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
* Remove Groovy infrastructure
abelsromero
force-pushed
the
refactor/migrate-AsciidoctorDoxiaParserTest-to-java
branch
from
221c3e3
to
3a34148
Compare
|
As a positive side-effect of groovy removal, we are one step closer to Java16 compatibility. Right now we are blocked by lombok in tests, but after removing it the next roadblock wwould have been groovy compilation due to the plugin we use. |
abelsromero
deleted the
refactor/migrate-AsciidoctorDoxiaParserTest-to-java
branch
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.
Thank you for opening a pull request and contributing to asciidoctor-maven-plugin!
What kind of change does this PR introduce? (check at least one)
What is the goal of this pull request?
Make code more approachable by migrating the tests to Java from Groovy.
Nothing bad about Groovy, but JUnit + AssertJ have come to offer similar ease of use.
In the long term, also simplifies the build by removing groovy compilation steps.
It also removes Groovy and Spock related configurations.
Are there any alternative ways to implement this?
No
Are there any implications of this pull request? Anything a user must know?
I am taking the opportunity to review the tests to remove duplication and unnecessary tests. But overall is a as-is migration.
Is it related to an existing issue?
Finally, please add a corresponding entry to CHANGELOG.adoc