[Bug 64027] This is regarding the below method - IOUtils.setByteArrayMaxOverride

https://bz.apache.org/bugzilla/show_bug.cgi?id=64027 --- Comment #2 from Sushmita Nag --- hi, So, is there any solution for the above issue ? As our Customer is totally blocked because of the above issue where in they are not able to upload a certain document of 2.5 MB because of

Re: Need help getting Specs for One Note versions older than 2012

On Mon, 23 Dec 2019, Nicholas DiPiazza wrote: Unfortunately, the formats are *drastically* different. Any attempt to reverse engineer would be a massive project... mostly impossible. Pesky. I have heard of that with products that get bought-in then redone, unusual for Microsoft fully in-house

Re: Need help getting Specs for One Note versions older than 2012

Thanks for the response Nick. Unfortunately, the formats are *drastically* different. Any attempt to reverse engineer would be a massive project... mostly impossible. I can use a java program based on the linux "strings" program which will make two passes through the older OneNote files. pass #

Re: Next version 4.2?

I saw a lot of @removal(4.2) and hence I've asked. I would now update those to @removal(5.0). My problem with cleaning up our technical debt is, that this often affects also the API and needs to be done on the major version change. In the other hand we like to have a stable API for a longer

Re: Need help getting Specs for One Note versions older than 2012

On Mon, 23 Dec 2019, Nicholas DiPiazza wrote: I'm needing some help gathering the older Spec documentation for Microsoft OneNote prior to year 2012. See https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-onestore/ae670cd2-4b38-4b24-82d1-87cfb2cc3725 and you'll notice that the

Need help getting Specs for One Note versions older than 2012

Dear Apache folks, I'm needing some help gathering the older Spec documentation for Microsoft OneNote prior to year 2012. See https://docs.microsoft.com/en-us/openspecs/office_file_formats/ms-onestore/ae670cd2-4b38-4b24-82d1-87cfb2cc3725 and you'll notice that the specifications are available

Re: Next version 4.2?

I agree with Mark that we should wait for 5.0.0 to remove more deprecated methods. Our previous policy was to wait 2 releases (eg 3.15 to 3.17) - can we agree that major releases like 5.0.0, 6.0.0 is when we will remove deprecated methods, in future?  On Monday 23 December 2019, 14:39:46

Re[2]: Next version 4.2?

Please fix the error related to the shiftRows method in POI 4.1.1 shiftRows don’t work Отправлено из мобильной Почты Mail.ru понедельник, 23 декабря 2019 г., 19:38 +0600 от jmarkmur...@gmail.com : >With Semantic versioning, you can't remove deprecates until a major version >change. > >On

Re: Next version 4.2?

This makes things a lot easier for folks using Maven for dependencies. What is the harm in letting things stay there until 5.0? On Mon, Dec 23, 2019 at 8:37 AM Mark Murphy wrote: > With Semantic versioning, you can't remove deprecates until a major > version change. > > On Sun, Dec 22, 2019 at

Re: Next version 4.2?

With Semantic versioning, you can't remove deprecates until a major version change. On Sun, Dec 22, 2019 at 3:46 PM Andreas Beeker wrote: > Hi, > > I'd like to remove the deprecates for 4.2. > > What will be our next version? > > Andi > > >

Build failed in Jenkins: POI-DSL-Maven #984

See Changes: [fanningpj] convert some tabs to spaces -- [...truncated 132.20 KB...] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in

[Bug 64027] This is regarding the below method - IOUtils.setByteArrayMaxOverride

https://bz.apache.org/bugzilla/show_bug.cgi?id=64027 PJ Fanning changed: What|Removed |Added OS||All --- Comment #1 from PJ Fanning ---