I dug some more into this and I think I found out what happened: The classes that you list as missing were still part in 3.10/3.10.1, but missing in newer beta-releases.
Via "git bisect" I could identify the commit r1620997 "Bug 56854 - XMLBeans performance when using getXXXList() and other proxy methods", as part of this change we switched from using *List() methods to *Array() methods in order to have better performance as the list methods in XMLBeans are known to be slow. So the removal of these classes is kind of "by design", as POI does not use them internally any more. The question is now how Tika should handle this? It may be able to also switch to *Array methods to also use the better performing way, otherwise we will need unit tests for all the missing items to get them included again, but that looks a bit like a workaround/hack... Dominik On Sat, Nov 8, 2014 at 1:22 PM, Nick Burch <[email protected]> wrote: > On Fri, 7 Nov 2014, Allison, Timothy B. wrote: >> >> I was able to get the schemas jar builder to add in the first by adding an >> empty test: > > > Thanks, added > >> Do we need to do this kind of thing for the other missing inner classes? > > > If the inner class is needed for a common use case (eg Tika), then we need a > unit test that touches said class. That should then see it correctly > included in poi-ooxml-schemas, assuming we haven't done something wrong with > that...! > > > Thanks > Nick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
