Are we ok with the backward incompatibilities in EMF...These are just a few. I realize these classes are @Internal, and the updates look great.
HwmfRecord.getRecordType() -> getWmfRecordType() oap.hemf.record.AbstractHemfComment -> oap.hemf.record.hemf.Comment oap.hemf.record.HemfRecord -> oap.h.r.emf.HemfRecord oap.hemf.record.HemfRecord -> oap.h.r.emf.HemfRecord oap.hemf.extractor.HemfExtractor -> oap.hemf.usermodel.HemfPicture On Sun, Apr 7, 2019 at 8:27 AM Yegor Kozlov <yegor.koz...@dinom.ru> wrote: > > +1 > > Looks good to me > > сб, 6 апр. 2019 г., 2:32 Greg Woolsey <greg.wool...@gmail.com>: > > > I've prepared artifacts for Apache POI release 4.1.0 (RC3). > > > > Notable changes since 4.0.1: > > > > * Improved support/fixes for Java 9+ and IBM JVM > > * New EMF renderer and support of SVG images in XSLF > > * Security, stability and memory/resource handling improvements > > * Various bug fixes across function and conditional format rule evaluation > > * Upgrade to XMLBeans 3.1.0 > > * Upgrade to Bouncycastle 1.61 > > * Upgrade to Curvesapi 1.06 > > * Upgrade to Commons-Codec 1.12 > > * Upgrade to Commons-Collections4 4.3 > > * Upgrade to XMLSec 2.1.2 > > > > https://dist.apache.org/repos/dist/dev/poi/4.1.0-RC3/ > > > > All tests pass. > > ASC signatures verify, key is in the KEYS file in /dist/dev/poi/. > > SHA* hashes match files. > > > > Latest regression run results looked good, Dominik was going to kick off > > another (probably still running) to verify some last minute changes cleared > > up some new errors found from augmented regression checks. > > > > Please vote on these artifacts. > > > > The vote is open until April 8, planning release announcement late that > > day. > > > > I'm +1 at this point, contents match 4.0.1, with updated dependency > > versions. > > > > Greg > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
