So I’ve thought a bit about this one. There are two things that ultimately got changed that impact end users AFAIK:
a) the various java bits are now on JDK 21 and some fixes for checkstyle issues and how they are built since the Apache POM got upgraded b) the container Any sort of compatibility testing should focus on those two things. The container I’ve been testing with my personal projects for the past month but they don’t exercise _everything_ in the container. In the past, we’ve just said “Yo! Container has new content!” and the feedback I’ve personally received was “Thanks! Was looking forward to new ptyhong/java/ruby/go/etc.” Now that we’ve got our build stable against the container as well, I’m feeling more confident about that part. (By far the biggest change is Python now enforcing how modules get installed. I think I’ve fixed that by disabling —user in pip and changing the location. End users will likely need to make that same flag change if they call test-patch manually/CI. We may want to flip that flag officially. If we do, it’d be better as its on PR.) That leaves the various Java bits. You pointed out the incompatibility I accidently slipped in trying to fix check style. (which I’ve hopefully reverted). I think _that’s_ the kind of testing we need. Is JDK 21 as the default jar ok? Did I mess up anything else switching out the Apache pom? I did a preliminary website check, but I need to do another one and push the current main branch live to the web pages yet. I think I’ll likely close out YETUS-1271 as complete and we’ll just pile in issues as new ones since the build appears to be stable. It should be all bug fixes from here on out. > On Apr 29, 2026, at 5:14 AM, Nick Dimiduk <[email protected]> wrote: > > What would be useful here Allen? Should we set up a parallel HBase build > that uses Yetus master? Maybe push a branch to the HBase repo with this > workflow installed and then PRs against that branch will run them both side > by side? > > On Wed, Apr 29, 2026 at 2:49 AM Allen Wittenauer <[email protected]> wrote: > >> FYI. >> >> These big jumps are always tricky when the action container is still >> behind. So I’ve gone ahead and merged this in to make it easier to work >> through the actual issues. >> >> Thanks. >> >>> On Mar 28, 2026, at 5:06 PM, Allen Wittenauer <[email protected]> wrote: >>> >>> Hi. >>> >>> I have a draft PR up for YETUS-1271. I think I have most of it working >> except for some of the maven/Java bits (it looks like it is failing >> javadoc). >>> >>> I’ll be honest. I haven’t done any JVM stuff in years (don’t even have >> any Java components in my stack really… it’s all C, python, and rust).. So >> I’ve been out of the loop for a long time. It would be great if someone >> coudl take a look and help get it over the finish line. I’m tempted to >> make a YETUS-1271 branch that we can all work off of until we get it >> working. >>> >>> Note that I went with Ubuntu 24.04. If we wait long enough, we may want >> to go with Ubuntu 26.04. It gets released as the newest LTS at the end of >> April. >>> >>> Thanks. >>> >>> >> >>
