mvel: fix broken build #14772
Open
mvel: fix broken build #14772
+2
−2
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
Due to the default branch of the MVEL project being switched to 3.x, which introduced custom dependencies (javaparser-mvel) from an unstandard repository, Maven dependency resolution failed; By explicitly switching back to the stable mvel2 branch, compatibility with the standard Maven Central Repository was restored, and the need for experimental components was eliminated at the root cause。
|
xingyaner is a new contributor to projects/mvel. The PR must be approved by known contributors before it can be merged. The past contributors are: hunsche, henryrneh |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Due to the default branch of the MVEL project being switched to 3.x, which introduced custom dependencies (javaparser-mvel) from an unstandard repository, Maven dependency resolution failed; By explicitly switching back to the stable mvel2 branch, compatibility with the standard Maven Central Repository was restored, and the need for experimental components was eliminated at the root cause。