Hi! While going through the open issues/PRs on GitHub something caught my eye, which I wanted to work on today:
org.apache.tapestry5.func.Tuple<A, B> has a custom #equals(Object) method, as it should have, being a container-type. But there's no appropriate #hashCode(), thereby violating a base contract of Java objects. This should be an easy fix. If it causes any trouble, it's most likely to using Tuple for something it wasn't supporting in the first place. IMO this should even be fixed in 5.6.x "TAP5-2657 Blacklist modules autoloaded via manifests" ( https://issues.apache.org/jira/browse/TAP5-2657) is commit/push-ready, but I don't want to add a new feature without any discussion/feedback first. There's no real pressure for both things to be included this particular release, though. Ben On Tue, Jan 5, 2021 at 11:24 PM Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > Hello, team! > > After this period of testing, I'm planning to cut releases of both 5.6.2 > and 5.7.0 and start threads for release votes. Does anyone have anything > else you'd want to include? > > Cheers! > > -- > Thiago >
