Re: writing XSSF broken in latest trunk

2013-08-20 Thread Nick Burch
On Tue, 20 Aug 2013, Dominik Stadler wrote: Unfortunately OpenOffice opens the file just fine... Pesky... Someone might be able to script something up using COM to launch Excel for a bunch of files, which might allow windows users to easily test, but I fear it'd be a lot more icky :/ Nick

Re: writing XSSF broken in latest trunk

2013-08-20 Thread Dominik Stadler
Unfortunately OpenOffice opens the file just fine... Dominik. On Tue, Aug 20, 2013 at 6:10 PM, Nick Burch wrote: > On Tue, 20 Aug 2013, Dominik Stadler wrote: > >> I have identified the commit below as being responsible, I have reverted >> it for now to ensure we do more investigation before p

Re: writing XSSF broken in latest trunk

2013-08-20 Thread Nick Burch
On Tue, 20 Aug 2013, Dominik Stadler wrote: I have identified the commit below as being responsible, I have reverted it for now to ensure we do more investigation before putting that fix into place once again. Unfortunately no unit test captured this, only Excel reported the files as being corr

Re: writing XSSF broken in latest trunk

2013-08-20 Thread Dominik Stadler
I have identified the commit below as being responsible, I have reverted it for now to ensure we do more investigation before putting that fix into place once again. Unfortunately no unit test captured this, only Excel reported the files as being corrupt if an empty "" element is in the xlsx. Revi

Re: writing XSSF broken in latest trunk

2013-08-20 Thread Yegor Kozlov
you need to create at least one sheet. a workbook without sheets is invalid. Yegor On Tue, Aug 20, 2013 at 5:52 PM, Dominik Stadler wrote: > Hi, > > I just found that xlsx-files produced by the latest builds of poi cannot be > opened in my version of Excel any more, anybody else have similar pr

writing XSSF broken in latest trunk

2013-08-20 Thread Dominik Stadler
Hi, I just found that xlsx-files produced by the latest builds of poi cannot be opened in my version of Excel any more, anybody else have similar problems or is this something related to my local environment? Even the simplest possible file already is reported corrupt for me, anybody seeing this