Re: [VOTE] Apache POI 4.1.2 release (RC1)

2020-01-31 Thread Alain FAGOT BÉAREZ
+1 - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org

[VOTE] Apache POI 4.1.2 release (RC1)

2020-01-31 Thread Andreas Beeker
Hi *, I've prepared artifacts for the release of Apache POI 4.1.2 (RC1). The most notable changes in this release are: - XDDF - some work on better chart support - Common SL / EMF - ongoing rendering fixes - see #60656 - XSLF - OOM fixes when parsing arbitrary shape ids + a new dependency to

Re: next release?

2020-01-31 Thread Andreas Beeker
I'm running into 4x OOMs when running the integration tests in Open or Oracle Jdk 8, even when raising the heap from 1512 to 2048 mb. This didn't happen with OpenJDK 12 - which was my default setting before :| It looks like there's a problem with XSLF (see below, although this is probably not

Re: next release?

2020-01-31 Thread Andreas Beeker
Hi, although I've fixed two issues *) locally, I'll postpone those commits after the release. So I would roll the release now. If there are any late-commits ... not a problem, but please inform us before Dominik and Tim run the integration tests again - not sure if this still makes sense, as

[Bug 64108] unsafe pipe character ("|") in Relationship target attribute is not being encoded into a '%7C'

2020-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64108 --- Comment #5 from Richard Costine --- I think that the original patch I provided should be the correct behavior, since the RFC indicates that the pipe character is not considered "valid" in a url, and would normally be encoded with a "%7C".

[Bug 64108] unsafe pipe character ("|") in Relationship target attribute is not being encoded into a '%7C'

2020-01-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64108 --- Comment #4 from PJ Fanning --- We don't typically support system properties. You've caught us in the middle of a release. If your patch is not the best behaviour for this code and only suits your use case, then we need to remove it. The