Re: Evaluating expressions outside a cell value context

[Greg Woolsey]

Oh, the primary class is o.a.p.ss.formula.DataValidationEvaluator

On Wed, Feb 1, 2017 at 5:37 PM Greg Woolsey  wrote:

> My GitHub branch now contains Data Validation code and unit tests.  The
> test file DataValidationEvaluations.xlsx contains a large set of validation
> examples, including one formula example that applies to a range of cells
> and uses a relative formula.  The evaluation code has corresponding logic
> to offset the relative formula Ptgs from the top left of the region.
>
> Every test is labeled in the file with column A as a description, column B
> as the cell with validation, and column C the expected result, TRUE =
> valid, FALSE = invalid.
>
> The unit test compares the POI validation result with the expected column,
> failing on boolean mismatches.
>
> Have not had time to run all tests yet, but this should only be code
> additions, not modifications.  I'll run them soon.
>
> I'm sure there are code style discussions to be had - for example I
> implemented some things as inner classes for now, but we may want them
> top-level instead.
>
> Comments welcome, this is early code but is built on top of the SS
> interfaces, so should be stable for HSSF and XSSF.
>
> Greg
>
> On Mon, Jan 30, 2017 at 9:55 AM Greg Woolsey 
> wrote:
>
> Also, I just found this sample workbook
> 
>  in
> the Excel online support docs.  If I have time to turn that into a unit
> test, it's about as complete as we could want.  Some parts are lost saving
> as HSSF, but we can then test that we evaluate what remains the same way as
> newer Excel when opening a legacy formatted file.
>
> On Mon, Jan 30, 2017 at 9:38 AM Greg Woolsey 
> wrote:
>
> Thanks, that makes sense wrt custom implementations of FormulaEvaluator -
> I hadn't thought about anyone rolling their own, but it's an interface, so
> quite possible.  Too bad we can't require Java 8 yet and use default
> methods.
>
> I can work with the new *Evaluator class idea.  And the HSSF limitations
> will just mean more unit tests :)  I have Excel 2016 available so I can
> create test workbooks, save them as both XLSX and XLS, and compare
> evaluations.  I can then write unit tests based on them that expect the
> results seen in Excel.  That should give us reference points for confidence
> in our replication of their logic, especially around rule priority/order
> and XLS HSSF files.
>
> On Fri, Jan 27, 2017 at 11:05 PM Nick Burch  wrote:
>
> On Sat, 28 Jan 2017, Greg Woolsey wrote:
> > As noted in one of the method JavaDocs, we also need to expose and make
> use
> > of the ConditionalFormattingRule "priority" attribute.  That's key to
> > matching the right rule when more than one rule applies to a cell.  Only
> > the first match in priority order is applied.
>
> Your slight challenge is that not all Conditional Formatting rules have a
> priority... XLSX ones do, and newer XLS ones based on CFRule12Record (sid
> = 0x087A) do, but the older XLS ones (CFRuleRecord / 0x01B1) don't. I'm
> not sure what Excel does for those, but my hunch (based on our API) is
> that it uses their order as a priority.
>
>
> > I've created a fork in GitHub for this, and committed a stab at
> > high-level API methods that could be added to the FormulaEvaluator
> > interface:
> >
> https://github.com/WoozyG/poi/commit/d44fee7bd03ed450af589467ec90e2581b9f2b16$
>
> FormulaEvaluator is an interface, which we have 4 implementations of in
> our codebabse, and I'd guess that other complex users of POI will have
> dozens more. I'm not sure, therefore, that we want to be putting all of
> the CF and DV logic methods on there, especially as it'll be common to all
> implementations
>
> The HSSF classes for CF all use org.apache.poi.ss.formula.Formula which is
> PTG based. The HSSF classes for DV seem to store the raw PTGs.
>
> If we added two new SS usermodel classes, eg
> ConditionalFormattingEvaluator and DataValidationEvaluator, these could be
> classes (not interfaces) with your proposed new methods on. They could
> hold the logic (once) for all formats (as it's basically the same on all)
> for priority, checking etc
>
> Doing that would also mean that "our" new classes could call out to our
> existing low-level ones to evaluate formulas. That would mean we wouldn't
> have to make a breaking change to the FormulaEvaluator interface too
>
> Might that work for you?
>
> > No implementations have been done yet, and the Vaadin comments indicate
> > HSSF doesn't parse conditional formatting properly or something, and
> can't
> > be evaluated correctly currently.  I don't know exactly what they found
> > wrong, and it's rather annoying they didn't file any bugs.
>
> I think that comment is out of date, from before the CF work in 3.13
>
> Nick
>
> 

Re: Evaluating expressions outside a cell value context

[Greg Woolsey]

My GitHub branch now contains Data Validation code and unit tests.  The
test file DataValidationEvaluations.xlsx contains a large set of validation
examples, including one formula example that applies to a range of cells
and uses a relative formula.  The evaluation code has corresponding logic
to offset the relative formula Ptgs from the top left of the region.

Every test is labeled in the file with column A as a description, column B
as the cell with validation, and column C the expected result, TRUE =
valid, FALSE = invalid.

The unit test compares the POI validation result with the expected column,
failing on boolean mismatches.

Have not had time to run all tests yet, but this should only be code
additions, not modifications.  I'll run them soon.

I'm sure there are code style discussions to be had - for example I
implemented some things as inner classes for now, but we may want them
top-level instead.

Comments welcome, this is early code but is built on top of the SS
interfaces, so should be stable for HSSF and XSSF.

Greg

On Mon, Jan 30, 2017 at 9:55 AM Greg Woolsey  wrote:

> Also, I just found this sample workbook
> 
>  in
> the Excel online support docs.  If I have time to turn that into a unit
> test, it's about as complete as we could want.  Some parts are lost saving
> as HSSF, but we can then test that we evaluate what remains the same way as
> newer Excel when opening a legacy formatted file.
>
> On Mon, Jan 30, 2017 at 9:38 AM Greg Woolsey 
> wrote:
>
> Thanks, that makes sense wrt custom implementations of FormulaEvaluator -
> I hadn't thought about anyone rolling their own, but it's an interface, so
> quite possible.  Too bad we can't require Java 8 yet and use default
> methods.
>
> I can work with the new *Evaluator class idea.  And the HSSF limitations
> will just mean more unit tests :)  I have Excel 2016 available so I can
> create test workbooks, save them as both XLSX and XLS, and compare
> evaluations.  I can then write unit tests based on them that expect the
> results seen in Excel.  That should give us reference points for confidence
> in our replication of their logic, especially around rule priority/order
> and XLS HSSF files.
>
> On Fri, Jan 27, 2017 at 11:05 PM Nick Burch  wrote:
>
> On Sat, 28 Jan 2017, Greg Woolsey wrote:
> > As noted in one of the method JavaDocs, we also need to expose and make
> use
> > of the ConditionalFormattingRule "priority" attribute.  That's key to
> > matching the right rule when more than one rule applies to a cell.  Only
> > the first match in priority order is applied.
>
> Your slight challenge is that not all Conditional Formatting rules have a
> priority... XLSX ones do, and newer XLS ones based on CFRule12Record (sid
> = 0x087A) do, but the older XLS ones (CFRuleRecord / 0x01B1) don't. I'm
> not sure what Excel does for those, but my hunch (based on our API) is
> that it uses their order as a priority.
>
>
> > I've created a fork in GitHub for this, and committed a stab at
> > high-level API methods that could be added to the FormulaEvaluator
> > interface:
> >
> https://github.com/WoozyG/poi/commit/d44fee7bd03ed450af589467ec90e2581b9f2b16$
>
> FormulaEvaluator is an interface, which we have 4 implementations of in
> our codebabse, and I'd guess that other complex users of POI will have
> dozens more. I'm not sure, therefore, that we want to be putting all of
> the CF and DV logic methods on there, especially as it'll be common to all
> implementations
>
> The HSSF classes for CF all use org.apache.poi.ss.formula.Formula which is
> PTG based. The HSSF classes for DV seem to store the raw PTGs.
>
> If we added two new SS usermodel classes, eg
> ConditionalFormattingEvaluator and DataValidationEvaluator, these could be
> classes (not interfaces) with your proposed new methods on. They could
> hold the logic (once) for all formats (as it's basically the same on all)
> for priority, checking etc
>
> Doing that would also mean that "our" new classes could call out to our
> existing low-level ones to evaluate formulas. That would mean we wouldn't
> have to make a breaking change to the FormulaEvaluator interface too
>
> Might that work for you?
>
> > No implementations have been done yet, and the Vaadin comments indicate
> > HSSF doesn't parse conditional formatting properly or something, and
> can't
> > be evaluated correctly currently.  I don't know exactly what they found
> > wrong, and it's rather annoying they didn't file any bugs.
>
> I think that comment is out of date, from before the CF work in 3.13
>
> Nick
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

Jenkins build is back to normal : POI-DSL-1.8 #59

[Apache Jenkins Server]

See 


-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Jenkins build is back to normal : POI-DSL-1.6 #135

[Apache Jenkins Server]

See 


-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

[Allison, Timothy B.]

Thank you, Dominik!

Looks like there is one other new one -- very rare -- that isn't caused by the 
embedded extractor or the WMF component.

java.lang.NegativeArraySizeException
at 
o.a.p.ddf.EscherComplexProperty.resizeComplexData(EscherComplexProperty.java:102)
at 
o.a.p.ddf.EscherArrayProperty.setArrayData(EscherArrayProperty.java:169)
at 
o.a.p.ddf.EscherPropertyFactory.createProperties(EscherPropertyFactory.java:81)
at 
o.a.p.ddf.AbstractEscherOptRecord.fillFields(AbstractEscherOptRecord.java:55)
at 
o.a.p.ddf.EscherContainerRecord.fillFields(EscherContainerRecord.java:81)
at 
o.a.p.ddf.EscherContainerRecord.fillFields(EscherContainerRecord.java:81)
at 
o.a.p.ddf.EscherContainerRecord.fillFields(EscherContainerRecord.java:81)
at 
o.a.p.ddf.EscherContainerRecord.fillFields(EscherContainerRecord.java:81)
at 
o.a.p.hwpf.model.EscherRecordHolder.fillEscherRecords(EscherRecordHolder.java:56)
at o.a.p.hwpf.model.EscherRecordHolder.(EscherRecordHolder.java:45)
at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:275)
at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:157)
at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:145)
at o.a.p.stress.HWPFFileHandler.handleFile(HWPFFileHandler.java:32)
at 
org.dstadler.commoncrawl.FileHandlingRunnable.run(FileHandlingRunnable.java:64)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1161)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:844)

[Bug 60677] Invalid substring range in WMF drawString

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60677

Tim Allison  changed:

   What|Removed |Added

 OS||All
Summary|Invalid substring range in  |Invalid substring range in
   |WMF draw|WMF drawString

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60677] New: Invalid substring range in WMF draw

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60677

Bug ID: 60677
   Summary: Invalid substring range in WMF draw
   Product: POI
   Version: 3.16-dev
  Hardware: PC
Status: NEW
  Severity: normal
  Priority: P2
 Component: POI Overall
  Assignee: dev@poi.apache.org
  Reporter: talli...@mitre.org
  Target Milestone: ---

Created attachment 34707
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=34707=edit
Triggering file

Dominik Stadler's recent regression tests identified an invalid substring range
exception triggered by WMF's drawString.

I extracted the triggering wmf from the file in Dominik's regression corpus,
and I'm attaching it here.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

[Dominik Stadler]

Hi,

results from the mass-testing are in, see
http://people.apache.org/~centic/poi_regression/reports/ for the comparison
between 3.15 and 3.16-beta2, a few newly introduced exceptions, almost all
related to the new EmbeddedExtractor and one exception in HwmfGraphics,
both areas where we added new functionality as far as I remember.

Full results are available at
http://people.apache.org/~centic/poi_regression/reportsAll/

Dominik.


On Wed, Feb 1, 2017 at 1:10 PM, Allison, Timothy B. 
wrote:

> > had some trouble with JDK crashes in Jpeg handling code
>
> Whoa...
>
> Thank you, Dominik!  And, thank you, Javen!
>
> -Original Message-
> From: Dominik Stadler [mailto:dominik.stad...@gmx.at]
> Sent: Wednesday, February 1, 2017 12:27 AM
> To: POI Developers List 
> Subject: RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)
>
> My testing is still running, had some trouble with JDK crashes in Jpeg
> handling code, but as you said it's just a beta.
>
> Dominik.
>
> On Feb 1, 2017 03:11, "Javen O'Neal"  wrote:
>
> > Alright. Just a beta. I'll release it in a few hours.
> >
> > On Jan 31, 2017 17:49, "Allison, Timothy B."  wrote:
> >
> > Argh...sorry, no time this go around...
> >
> > -Original Message-
> > From: Javen O'Neal [mailto:one...@apache.org]
> > Sent: Tuesday, January 31, 2017 8:19 PM
> > To: POI Developers List 
> > Subject: Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)
> >
> > Should I wait for the results of common crawl or other regression
> > testing before proceeding with the release?
> >
> > On Jan 30, 2017 16:19, "Andreas Beeker"  wrote:
> >
> > > +1 from me
> > >
> > > I have only done a shallow check of the - not any more - usual
> > > suspects, as I'm quite busy with other stuff ... sorry
> > >
> > > Thank you Javen for taking care of this.
> > >
> > > Andi
> > >
> > >
> > > 
> > > - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For
> > > additional commands, e-mail: dev-h...@poi.apache.org
> > >
> > >
> >
>

Re: Saving modified Workbook in place

[Nick Burch]

On Wed, 1 Feb 2017, Murphy, Mark wrote:
I thought that there was a way to save a workbook in place when using a 
File type input. But I can't find the secret sauce.


The method will be write() with no arguments:
https://poi.apache.org/apidocs/org/apache/poi/POIDocument.html#write()

Off the top of my head, I can't remember how much more work there is to do 
to finish the HSSF support for it...


Nick

-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Re: Saving modified Workbook in place

[Javen O'Neal]

https://bz.apache.org/bugzilla/show_bug.cgi?id=57919

This bug is still open as it hasn't been fully implemented for all
constructors and factories yet.

On Feb 1, 2017 06:50, "Murphy, Mark"  wrote:

> I thought that there was a way to save a workbook in place when using a
> File type input. But I can't find the secret sauce. If I open a Workbook
> using WorkbookFactory(new File(filename)); I cannot write to an output
> stream based on the same file name. If I write the modified workbook to an
> output stream based on a different file name, the original file is updated,
> but now I have a second file. If I do not write the changes, but instead
> just close the workbook, it does not create the second file, but it also
> does not update the existing file.
>
> So how can I update an existing spreadsheet without creating a secondary
> file? I am guessing that if I use an InputStream to open the initial file,
> I can write the updated workbook to an OutputStream without the original
> being updated?
>

Saving modified Workbook in place

[Murphy, Mark]

I thought that there was a way to save a workbook in place when using a File 
type input. But I can't find the secret sauce. If I open a Workbook using 
WorkbookFactory(new File(filename)); I cannot write to an output stream based 
on the same file name. If I write the modified workbook to an output stream 
based on a different file name, the original file is updated, but now I have a 
second file. If I do not write the changes, but instead just close the 
workbook, it does not create the second file, but it also does not update the 
existing file.

So how can I update an existing spreadsheet without creating a secondary file? 
I am guessing that if I use an InputStream to open the initial file, I can 
write the updated workbook to an OutputStream without the original being 
updated?

Build failed in Jenkins: POI-DSL-1.8 #58

[Apache Jenkins Server]

See 

Changes:

[onealj] echo release version

[onealj] ignore compile-lib/svnant

[onealj] release-prep1 should abort if release tag already exists. It's likely 
that the version was entered incorrectly or copy-pasted from a template.

--
[...truncated 2762 lines...]
[junit] Reading document/documentProtection_trackedChanges_no_password.docx 
with class org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/documentProtection_trackedChanges_no_password.docx 
with class org.apache.poi.stress.OPCFileHandler
[junit] Reading document/drawing.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/drawing.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/empty.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/endingnote.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/endnotes.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/endnotes.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/equation.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/footnote.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/footnotes.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/footnotes.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/form_footnotes.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/form_footnotes.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/headerFooter.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/headerFooter.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/headerPic.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/headerPic.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/header_image.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/heading123.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/heading123.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/hyperlink.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/innertable.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/issue_51265_1.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/issue_51265_1.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/issue_51265_2.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/issue_51265_2.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/issue_51265_3.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/issue_51265_3.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/lists-margins.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/nature1.gif with class 
org.apache.poi.TestAllFiles$NullFileHandler
[junit] Reading document/nature1.jpg with class 
org.apache.poi.TestAllFiles$NullFileHandler
[junit] Reading document/nature1.png with class 
org.apache.poi.TestAllFiles$NullFileHandler
[junit] Reading document/nature2.jpg with class 
org.apache.poi.TestAllFiles$NullFileHandler
[junit] Reading document/nature3.jpg with class 
org.apache.poi.TestAllFiles$NullFileHandler
[junit] Reading document/nature4.jpg with class 
org.apache.poi.TestAllFiles$NullFileHandler
[junit] Reading document/o_kurs.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/ob_is.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/page-break-before.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/page-break.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/pageref.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/parentinvguid.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/picture.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/pictures_escher.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/protected_sample.docx with class 
org.apache.poi.stress.XWPFFileHandler
[junit] Reading document/protected_sample.docx with class 
org.apache.poi.stress.OPCFileHandler
[junit] Reading document/rasp.doc with class 
org.apache.poi.stress.HWPFFileHandler
[junit] Reading document/sample.docx with class 
org.apache.poi.stress.XWPFFileHandler

RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

[Allison, Timothy B.]

> had some trouble with JDK crashes in Jpeg handling code

Whoa...

Thank you, Dominik!  And, thank you, Javen!

-Original Message-
From: Dominik Stadler [mailto:dominik.stad...@gmx.at] 
Sent: Wednesday, February 1, 2017 12:27 AM
To: POI Developers List 
Subject: RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

My testing is still running, had some trouble with JDK crashes in Jpeg handling 
code, but as you said it's just a beta.

Dominik.

On Feb 1, 2017 03:11, "Javen O'Neal"  wrote:

> Alright. Just a beta. I'll release it in a few hours.
>
> On Jan 31, 2017 17:49, "Allison, Timothy B."  wrote:
>
> Argh...sorry, no time this go around...
>
> -Original Message-
> From: Javen O'Neal [mailto:one...@apache.org]
> Sent: Tuesday, January 31, 2017 8:19 PM
> To: POI Developers List 
> Subject: Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)
>
> Should I wait for the results of common crawl or other regression 
> testing before proceeding with the release?
>
> On Jan 30, 2017 16:19, "Andreas Beeker"  wrote:
>
> > +1 from me
> >
> > I have only done a shallow check of the - not any more - usual 
> > suspects, as I'm quite busy with other stuff ... sorry
> >
> > Thank you Javen for taking care of this.
> >
> > Andi
> >
> >
> > 
> > - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For 
> > additional commands, e-mail: dev-h...@poi.apache.org
> >
> >
>

[Bug 60626] ArrayIndexOutOfBoundsException in EvilUnclosedBRFixingInputStream

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60626

Andreas Beeker  changed:

   What|Removed |Added

  Attachment #34663|text/plain  |application/xhtml+xml
  mime type||

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

[Bug 60670] Fails to create document nodes in MSI files larger than 2 GB

[bugzilla]

https://bz.apache.org/bugzilla/show_bug.cgi?id=60670

Markus Kilås  changed:

   What|Removed |Added

 CC||jmarkus+apach...@kilas.se

-- 
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org