Re: Beta time yet?

ah, you are right, I did not find that one with the search terms that I was using... Dominik. On Thu, Apr 28, 2016 at 2:22 PM, Allison, Timothy B. wrote: > >However I unearthed https://bz.apache.org/bugzilla/show_bug.cgi?id=58963 > >and

RE: Beta time yet?

>However I unearthed https://bz.apache.org/bugzilla/show_bug.cgi?id=58963 >and https://bz.apache.org/bugzilla/show_bug.cgi?id=57031 which I think were >the bugs for the change. Maybe they >contain the files you are looking for? Thank you for the links, Dominik! I finally dug up what I was

Re: Beta time yet?

Hi, I'm still fiddling with the release script - and need to try it out, which leads to already changed version-ids. Currently pinning the documentation (i.e. svn:externals) doesn't work - please be patient with me. Andi. On 30.03.2016 23:30, Nick Burch wrote: > I've had a go at adding some

RE: Beta time yet?

01, 2016 4:13 PM To: POI Developers List <dev@poi.apache.org> Subject: Re: Beta time yet? Hi, the POI specific regression test report is now updated for comparing 3.14-beta2 (nearly 3.14 final) with the current 3.15-beta1 (as of Tuesday) at http://people.apache.org/~centic/poi_regression/r

Re: Beta time yet?

Yep, I think it is some missing class in the reduced schema-jar. If I add a unit-test that triggers this code, the error goes away. I will commit this test tomorrow to avoid this issue in the future. Dominik. On Fri, Apr 1, 2016 at 11:57 PM, Dominik Stadler wrote: >

Re: Beta time yet?

Hi, Yes, it is quite strange, I can currently reproduce it locally in the regression-test-project without any OOM, but not if I do the same thing in POI itself, seem to be somehow related to the full/partial -schema jars, I am testing some more to see why it happened here... If I try to access

Re: Beta time yet?

Hi Dominik, thanks again for running the regression tests. @issue 1: I've tried to limit the classes to the lite-schemas, but the error doesn't show up. My guess is, the toArray fails when the children aren't returned as gd elements but as xmlanytype [1]. Another wild guess is, I think

Re: Beta time yet?

to script more of the manual work ... - >> as we use Jenkins here at my $dayjob, I'm used to (nearly) >> one-click-releasing >> the artifacts - I guess something like this would be possible with Ant too >> ... >> >> Andi >> >> >> >> -- >> V

RE: Beta time yet?

This is a new module contained in 2 new files plus a unit test, so it's understandable that it would be a larger commit. Your code style and documentation is great, despite Java being a verbose beast. I'm spending most of my time making sure it meshes well with the current code base and that

RE: Beta time yet?

On Thu, 31 Mar 2016, Murphy, Mark wrote: If you have any questions or comments, I would love to hear your feedback. I haven't looked at this patch of yours. However... Several small patches are easier to review and apply than one big, for un-related fixes or improvements. However, one big

RE: Beta time yet?

ent way, I would like to know what it is, and the reasoning for it. -Original Message- From: Javen O'Neal [mailto:javenon...@gmail.com] Sent: Thursday, March 31, 2016 12:12 PM To: POI Developers List Subject: RE: Beta time yet? I've been slowly reviewing 58787. It's a larger patch, so ta

RE: Beta time yet?

ginal Message- > From: Nick Burch [mailto:n...@apache.org] > Sent: Wednesday, March 30, 2016 5:50 PM > To: POI Developers List > Subject: RE: Beta time yet? > > On Wed, 30 Mar 2016, Allison, Timothy B. wrote: > > I added a new report "mime_diffs_A_to_B_details.xlsx&

RE: Beta time yet?

Can we get bug 58787 into the Beta? -Original Message- From: Nick Burch [mailto:n...@apache.org] Sent: Wednesday, March 30, 2016 5:50 PM To: POI Developers List Subject: RE: Beta time yet? On Wed, 30 Mar 2016, Allison, Timothy B. wrote: > I added a new rep

RE: Beta time yet?

On Wed, 30 Mar 2016, Allison, Timothy B. wrote: I added a new report "mime_diffs_A_to_B_details.xlsx", which I'll send to you privately shortly. I can share this if anyone wants it, and it will be included in all future report dumps. Checking a few from there, I think the detection as only

Re: Beta time yet?

On Wed, 30 Mar 2016, kiwiwings wrote: This time I think about ant-scripting the svn changes, e.g. un-/pinning of the docs, creating the branch, uploading the artifacts. I'd like to have something like: - ant release-beta - ant release-final I've had a go at adding some things for this in

Re: Beta time yet?

ting the svn changes, e.g. un-/pinning of the docs, creating the branch, uploading the artifacts. I'd like to have something like: - ant release-beta - ant release-final Andi -- View this message in context: http://apache-poi.1045710.n5.nabble.com/Beta-time-yet-tp5722477p5722487.html Sent from t

Re: Beta time yet?

On Wed, 30 Mar 2016, kiwiwings wrote: Maybe I should spent some time to script more of the manual work ... - as we use Jenkins here at my $dayjob, I'm used to (nearly) one-click-releasing the artifacts - I guess something like this would be possible with Ant too ... My vague recollection is

RE: Beta time yet?

On Wed, 30 Mar 2016, Allison, Timothy B. wrote: The only differences in exceptions were caused by Tika now identifying several files as xlsx vs zip or ooxml...which I can't explain. I did some work on improving exceptions in 3.14 for POIFS given non-POIFS stuff, and since then on OPCPackage

Re: Beta time yet?

this message in context: > http://apache-poi.1045710.n5.nabble.com/Beta-time-yet-tp5722477p5722481.html > Sent from the POI - Dev mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > >

Re: Beta time yet?

poi.1045710.n5.nabble.com/Beta-time-yet-tp5722477p5722481.html Sent from the POI - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org

RE: Beta time yet?

30, 2016 7:05 AM To: POI Developers List <dev@poi.apache.org> Subject: Re: Beta time yet? Hi, I'm generally in favor of more releases to reduce the amount of time that people need to wait for fixes, our unit-tests and other ways of testing should catch the majority of problems quickly

Re: Beta time yet?

On Wed, 30 Mar 2016, Dominik Stadler wrote: I'm generally in favor of more releases to reduce the amount of time that people need to wait for fixes, our unit-tests and other ways of testing should catch the majority of problems quickly nowadays and if the next release is coming up soon anyway, a

Re: Beta time yet?

Hi, I'm generally in favor of more releases to reduce the amount of time that people need to wait for fixes, our unit-tests and other ways of testing should catch the majority of problems quickly nowadays and if the next release is coming up soon anyway, a regression looses some of it's horror as

Beta time yet?

Hi All I know it's not been very long at all since 3.14, but we've fixed a decent number of bugs already, including one for which Tika is awaiting a fix (TIKA-1836). What do people think about doing a beta release in a few weeks time, to get those fixes out to our users? I figure we might