Sorry, but that does not answer my question as to why the ticket was deleted rather than just being closed (e.g. as a duplicate)?
A closed ticket does not involve any work, otherwise why don't we delete all closed tickets? Whereas a deleted ticket that is referred to in various place does cause extra work. It has certainly caused me problems trying to follow the commits. Sebb On Tue, 4 Jul 2023 at 18:02, Gary Gregory <[email protected]> wrote: > > Because it doubles up the work form the original ticket. We do not need a > second ticket to track the same new feature IMO. > > Gary > > On Tue, Jul 4, 2023, 12:57 sebb <[email protected]> wrote: > > > Why did you delete this ticket? > > > > It is referred to in various emails and commit messages, so it is > > confusing that the ticket does not exist. > > > > I think only tickets which are spam should be deleted. > > > > Sebb > > > > On Mon, 3 Jul 2023 at 12:04, Gary D. Gregory (Jira) <[email protected]> > > wrote: > > > > > > > > > [ > > https://issues.apache.org/jira/browse/LANG-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > ] > > > > > > Gary D. Gregory deleted LANG-1647: > > > ---------------------------------- > > > > > > > > > > Add and ExceptionUtils.isChecked() and isUnchecked() > > > > ---------------------------------------------------- > > > > > > > > Key: LANG-1647 > > > > URL: https://issues.apache.org/jira/browse/LANG-1647 > > > > Project: Commons Lang > > > > Issue Type: Improvement > > > > Reporter: Arturo Bernal > > > > Priority: Minor > > > > Time Spent: 3.5h > > > > Remaining Estimate: 0h > > > > > > > > The idea it's have a function that check if a given throwable is a > > checked exception. There are some similar function in ConcurrentUtils, but > > have package visibility and return the same exception. > > > > Seem logic have this verification in the class that have this > > responsibility - ExceptionUtils > > > > > > > > > > > > -- > > > This message was sent by Atlassian Jira > > > (v8.20.10#820010) > >
