On Thu, 28 May 2015, Andreas Beeker wrote:
In the context of the jackcess-discussion, I'd even more prefer, if we
split those components to separate jars having the X/H??F classes
together.
It certainly used to be the case that some users didn't want the X##F
family of documents, and didn't
Nick Burch-2 wrote
It certainly used to be the case that some users didn't want the X##F
family of documents, and didn't want larger extra dependencies that they
needed, so they liked us keeping the split. With the special way that
Android does things like javax.xml, I believe that this
Yes, it's not good, but at least for 3.12 it seems to be the case, I
just found out the day before when I tried to use XWPFDocument myself.
BTW, it was introduced via commit Stub a common WP paragraph class,
needs uncommenting as XWPF implements/emulates, r1657712 in February,
we likely can just
Ideally we should have the core classes/interfaces in the main jar, so that
the ooxml classes can work without scratchpad. I'd say it's fine for
scratchpad to depend on core, ooxml to depend on core, not sure about ooxml
(nominally stable) depending on scratchpad (nominally not)
What does
On Wed, 27 May 2015, cen...@apache.org wrote:
adjust instructions for XWPF to note that scratchpad-jar is needed as well
Should that be the case though?
Ideally we should have the core classes/interfaces in the main jar, so
that the ooxml classes can work without scratchpad. I'd say it's
