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? Andi. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
