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 move the one class into main to be fine again. I have entered https://bz.apache.org/bugzilla/show_bug.cgi?id=57963 to not forget about the documentation side when this is done. Dominik. On Thu, May 28, 2015 at 12:38 AM, Andreas Beeker <[email protected]> wrote: >> 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 everyone else think? > > I haven't checked the background of what xwpf depends on in scratchpad, but > if it's not a big chunk of classes, I'd prefer to move those to main. > 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. > > Andi > > > > --------------------------------------------------------------------- > 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]
