bumped jnr-posix version for m1 support #9762
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
tglman
force-pushed
the
develop
branch
2 times, most recently
from
25a21e4
to
9342fb2
Compare
kwin
added a commit
to kwin/jbake
that referenced
this pull request
Mar 14, 2022
kwin
added a commit
to kwin/jbake
that referenced
this pull request
Mar 14, 2022
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.
What does this PR do?
Bumps jnr-posix version to the latest one ( 3.1.15 )
Motivation
jnr-posix version 3.0.50 does not support newest M1 architecture. Bumping to the newest one fixes the problem.
Related issues
None
Additional Notes
ETL build fails, but it also does on develop, so I think the problem is not connected to this PR.
Checklist
[x] I have run the build using
mvn clean packagecommand[?] My unit tests cover both failure and success scenarios