Hi David, > And the suggested actions are: > * Do not merge ooxml-schemas and ooxml-security, but do add Maven > profiles allowing a switch between lite/full
I'd like to give another reason for the first point. The ooxml-schemas are based on the ECMA 376 1st Edition and are stable for a while. The other xmlbeans jars are quite recently and more likely to be changed - at least I hope to fix the certificate based encryption in the next year or so ... and maybe maybe, I'll move to jaxb for the encryption stuff - as I did for the geometry stuff of common sl. In my point of view, the only reason to provide a new ooxml-schemas would be, when we finally switch to a newer edition. (see #56205 for that) It would make things a bit more clear, what's actually inside the ooxml-schemas. Of course, I still the prefer the 2nd suggestion - but that's a bit more todo, as the schemas rely on each other, e.g. PPT -> ODraw. Andi -- View this message in context: http://apache-poi.1045710.n5.nabble.com/Merging-security-schema-to-full-schema-tp5720561p5720749.html Sent from the POI - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
