Gary Gregory
Gary Gregory
Fair enough. Any thoughts @elharo ?
You can also "erase" exceptions. See [org.apache.commons.io.function.Erase](https://github.com/apache/commons-io/blob/master/src/main/java/org/apache/commons/io/function/Erase.java): ``` // no throws in signature foo() { try { // Something that throws IOException } catch (final IOException ex) { rethrow(ex); //...
(Just for fun) A special and interesting example of APIs that return exceptions by design is JUnit's `assertThrows()` family of methods.
@theshoeshiner Note that the build is still red. Run `mvn` locally (by itself) before pushing to catch all errors.
Hello @mkoncek How can this goal be enforced such that this build fails without the change?
How is this any different from `org.apache.commons.lang3.ArrayUtils.contains(Object[], Object)`? If we do anything, I could see using a solution like @aherbert points out. The disadvantage is that it creates an new...
Hello @mfg92 > What can I do to move this issue forward? You need to gather positive consensus from the community, which I do not see ATM.
Hello @mfg92 How about using the existing API, like this (from `ArrayUtilsTest`): ```java @Test public void testContainsAnyEnum() { assertTrue(ArrayUtils.containsAny(ElementType.values(), ElementType.ANNOTATION_TYPE)); assertFalse(ArrayUtils.containsAny(ElementType.values(), (ElementType) null)); } ``` ?
Closing: No reply in over 3 weeks.
Hello @lorban, Thank you for working on this! Could the TLS failures be false positives?