Y, I agree with Nick. I'm slightly inclined to not using Commons IO to avoid potential conflicts, but I defer to the more active devs :).
We can't do the equivalent of a maven-shade-plugin in Ant, can we? Looks like maybe in gradle...but... -----Original Message----- From: Nick Burch [mailto:apa...@gagravarr.org] Sent: Tuesday, January 17, 2017 3:35 PM To: POI Developers List <dev@poi.apache.org> Subject: Re: Using Apache Commons IO On Tue, 17 Jan 2017, Javen O'Neal wrote: > In the spirit of "the best code is no code", how would you feel about > replacing our endian classes and IOUtils with Apache Commons IO? > > The downside is that it adds a dependency. > https://poi.apache.org/overview.html#components How many classes do we need? Do those classes include all the methods we need, or are there gaps? (Having dealt with yet another StackOverflow question today from someone stuck on a really old POI version, and knowing that the ones who make it to StackOverflow are actually the better ones, I'd rather inline a few classes / do nothing instead of adding a dependency that people can get wrong....) Nick --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
