Bump byte-buddy, gradle, lombok #159
Open
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
hughsimpson
changed the title
hughsimpson
force-pushed
the
bump_byte-buddy
branch
from
98375d9
to
6cab998
Compare
hughsimpson
changed the title
|
@ivantopo @dpsoft I'm about to do a thing with another repo where it has to make a pr to yet another repo when a certain file changes. Once I do that thing, it'll probably be easy enough to do a similar thing here and make the jar construction traceable. Might do that instead for byte-buddy. Edit: attempt that flow here |
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.
Bumps some dependencies
I built byte-buddy off this manually applied diff with byte-buddy 15.1 according to the comments on this pr. I didn't apply the commented-out maven-shade-plugin from that diff, since that seemed like a mistake? Used Java version 1.8.0_392 (
OpenJDK Runtime Environment (Zulu 8.74.0.17-CA-macos-aarch64) (build 1.8.0_392-b08)) to build the byte-buddy jar.Perhaps, in the future, it would be possible to write a manually-triggered github action to do this (i.e. pass it a byte-buddy tag, and have it clone the repo, check out that tag, apply the diff, build the artifact, and pr the jars) so that provenance could be better ascertained... Obviously I haven't done that leg-work in this pr.
Other changes:
|&with2>&1 |because the former doesn't work on macos :'(