Also toward 2.0, we need to collapse: org.apache.commons.beanutils2.BeanUtilsBean org.apache.commons.beanutils2.BeanUtilsBean2
and org.apache.commons.beanutils2.ConvertUtilsBean org.apache.commons.beanutils2.ConvertUtilsBean2 and probably add classes in org.apache.commons.beanutils2.converters for URI, Path and UUID perhaps. PRs welcome. Gary On Mon, Oct 21, 2019 at 8:55 AM Gary Gregory <garydgreg...@gmail.com> wrote: > On Mon, Oct 21, 2019 at 2:53 AM Emmanuel Bourg <ebo...@apache.org> wrote: > >> Le 17/10/2019 à 19:45, Gary Gregory a écrit : >> >> > It seems like org.apache.commons.collections4.Predicate<T> can/should be >> > replaced by java.util.function.Function<T, R> >> >> Did we consider modifying collections4 such that Predicate extends >> Function? That would ease the transition to the Java 8 types. >> > > Happy Monday to all, > > Since the next version is 2.0, we can break backward compatibility and use > java.util.function directly. See git master where there is only one > remaining dependency on Commons Collections. > > See also https://issues.apache.org/jira/browse/BEANUTILS-527 for a few > more migratory details. > > I am thinking we can consider making the remaining dependency a private > static class or, implement the feature differently. I am looking for > opinions here... > > The other question is what to do with Collection's Transformer class. > There at the very least we can make it a subtype of Java's own Function. We > can also just deprecate Transformer in favor of Function. It depends on how > much value there is in a functional interface called "Transformer" vs the > more general "Function". I think in the end, Transformer should be > deprecated in favor of Function. > > Thoughts? > > Thank you! > Gary > > >> >> Emmanuel Bourg >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >>
