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
I always wonder why a lot of these oldies stick with POI 3.9 and based on your
explanation there wouldn't be much reason not to use 3.10 as there weren't much
breaking changes ... if any.
So it must be something else ... I start to believe - especially when dealing
with a few stackoverflow issue
I believe that one of the reasons people get stuck on really old versions of
POI is that inevitably there are breaking changes in nearly every release. So
folks pick a version, and it remains the one they use. If we were to shift to a
semantic versioning scheme where we only introduced breaking
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
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
https://commons.apache.org/proper/commons-io/javadocs/api-release/inde
https://bz.apache.org/bugzilla/show_bug.cgi?id=60031
Javen O'Neal changed:
What|Removed |Added
Attachment #34632|text/plain |application/x-gzip
mime type|
https://bz.apache.org/bugzilla/show_bug.cgi?id=60031
Andrzej Witecki changed:
What|Removed |Added
Status|NEEDINFO|NEW
--
You are receiving this mail
https://bz.apache.org/bugzilla/show_bug.cgi?id=60031
Andrzej Witecki changed:
What|Removed |Added
CC||sodoww+bz.apache.org@gmail.
