Work starting now on 3.15 RC3

2016-09-17 Thread David North
-- David North | www.dnorth.net signature.asc Description: OpenPGP digital signature

[Bug 60141] Executing a program in Eclipse is displaying an exception on the console: "Exception in thread "main" org.apache.poi.openxml4j.exceptions.OpenXML4JRuntimeException: Rule M2.4 exception"

2016-09-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60141 Dominik Stadler changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this

[VOTE] Apache POI 3.15 RC3

2016-09-17 Thread David North
Hi everyone, https://dist.apache.org/repos/dist/dev/poi/3.15-RC3/ Areas to review: * Does it work? * Are the sigs and hashes valid? * Have the issues with the last RC been fixed? * Are the release notes (inc requested additions from Javen) OK? The vote starts now and ends at 18:15 BST on Monday

Re: svn commit: r1761161 - /poi/trunk/build.xml

2016-09-17 Thread Javen O'Neal
Should the classifier be RC3? Looking at build.xml, this seems to only affect the output file name and not the maven artifact coordinates. If so, then this doesn't matter. On Sep 17, 2016 01:50, wrote: > Author: dnorth > Date: Sat Sep 17 08:50:18 2016 > New Revision: 1761161 > > URL: http://svn

Re: [VOTE] Apache POI 3.15 RC3

2016-09-17 Thread Javen O'Neal
Is this memory savings seen during regular use of POI, such as the following example, or only when explicitly created with user code calling lower level OPCPackage operations? If so, should release notes mention the lower memory usage for OOXML documents due to File Backed Data Source? Workbook wb

[Bug 59559] Rule M2.4 exception : this error should NEVER happen!

2016-09-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59559 Javen O'Neal changed: What|Removed |Added Resolution|LATER |INVALID --- Comment #3 from Javen O'Nea

Re: svn commit: r1761161 - /poi/trunk/build.xml

2016-09-17 Thread Andreas Beeker
On 17.09.2016 19:10, Javen O'Neal wrote: > Should the classifier be RC3? > > Looking at build.xml, this seems to only affect the output file name and > not the maven artifact coordinates. If so, then this doesn't matter. > When reworking the release scripts, I've removed a few naming parts (e.g. t