Ok, I've updated the release branch and pulled up what I think is the fix. I think we should also create an Apache POI ticket to complain about the behavior of class instantiation in the poi-ooxml package -- and also the backwards dependency between poi-ooxml.jar and poi.jar, on org.apache.poi.util. The way the classes depend on each other makes Apache POI unusable as separate jars, and the class loader issue means that it must always be loaded in the application root level. It's much better (and more standard) to use the current class's class loader when resolving classes by reflection.
Any volunteers for working with Apache POI to create such a ticket, and follow up? Karl On Thu, Aug 31, 2017 at 12:56 PM, Markus Schuch <[email protected]> wrote: > +1 for bugfix release > > Am 31. August 2017 14:55:16 MESZ schrieb Karl Wright <[email protected]>: > >Essentially, all Tika extractions for Microsoft Office files will fail > >without a fix for this problem, so I think it's pretty severe. What > >does > >everyone else think? > > > >Karl >
