On 24/10/15 07:34, Dustin Spicuzza wrote: > On 10/23/2015 12:03 PM, David North wrote: >> On 16/10/15 21:52, Andreas Beeker wrote: >>> Hi, >>> >>>> Nick proposed we should have an ooxml-schemas-1.2 JAR containing visio, >>>> security & main, rather than three separate artefacts. But keep the >>>> existing lightweight one too. All agreed this made sense. ACTION: >>>> Someone to implement this. >>> As this seems to be shortly before done - and the security schema is kind >>> of my "fault". >>> Do we really need to increase the size of the full schema? >>> >>> Or to formulate it even more cynical, if users don't read the faq or >>> component docs - >>> they won't find the missing classes neither in the full schemas nor in the >>> tripple. >>> >>> I personally prefer to have more smaller jars instead of a big one. >>> Ideally every format has its own xml-jar. >>> And to look a bit more into the future, I think the jaxb variant might be >>> also smaller than xmlbeans - >>> so speculating, small enough to include everything for the corresponding >>> format. >>> >>> How about adding a profile (with description) to the maven poms - so a user >>> can >>> switch between the lite/full/triple dependency version? >> Dustin, any thoughts? I have some work time allocated to POI next week >> and am keen to do what I can to progress us towards 3.14 beta1 >> >> Thanks, >> David >> > Hey David, > > I'm not much of an expert on the schema stuff, so I don't have much to > add here. I got the visio stuff added and incremented the version to 1.2 > (and it's in trunk now), but once I started looking at combining the > security jars it looks like it has special settings and such... so I'd > rather someone else who knows how to test it to deal with it rather than > myself. If that person is you, by all means go for it. :) > > I've pushed all of the XDGF changes that I have for now. I'm hoping to > get some more test coverage added at some point.
OK, so just to summarize the situation, as it's taken me a while to get it fully straight in my mind: In the 3.13 release, we had: poi-ooxml-schemas-3.13-20150929.jar at 5.4MB. This is the 'lite' JAR recommended for normal use, containing relevant parts of all supported formats + security. And if you wanted more, you used ooxml-schemas-1.1, which is versioned/released separately to POI and is currently 14.2MB. You might also use ooxml-security at a further 1.3MB Currently on trunk, we have: poi-ooxml-schemas is up to 5.6MB following the inclusion of the Visio schemas meanwhile, ooxml-schemas is up to 15MB and ooxml-security remains 1.3MB. And the suggested actions are: * Do not merge ooxml-schemas and ooxml-security, but do add Maven profiles allowing a switch between lite/full * Consider adding profiles per-format to allow working with just the full schemas for that format, in a JAR of their own. I'll also have a go at improving the description of all this on the website. Thanks, David -- David North, Technical Lead, CoreFiling Limited http://www.corefiling.com Phone: +44-1865-203192 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
