[#529] javaparser v3 migration #530
Merged
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
…11 to com.github.javaparser:javaparser-core:2.5.1
laurentschoelens
added
enhancement
dependencies
laurentschoelens
changed the title
|
This change probably belongs in a minor rev bump vs a point release. |
laurentschoelens
force-pushed
the
jt-529
branch
2 times, most recently
from
e3c7baa
to
a07c5fb
Compare
laurentschoelens
force-pushed
the
jt-529
branch
from
a07c5fb
to
54782b7
Compare
|
Updating PR move to latest 3.X javaparser since migration is OK now 😄 |
mattrpav
changed the title
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.
Fixes #529 by moving from
com.google.code.javaparser:javaparser:1.0.11tocom.github.javaparser:javaparser-core:latest