Open hughsimpson opened 2 months ago
@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
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 :'(