https://bz.apache.org/bugzilla/show_bug.cgi?id=62625
--- Comment #7 from Tim Allison ---
And fix made to ensure closing of streams from lgtm. Thank you, again, PJ.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62625
Tim Allison changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=62625
Tim Allison changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bz.apache.org/bugzilla/show_bug.cgi?id=62625
--- Comment #4 from PJ Fanning ---
The recent code changes seem to have introduced a number of new warnings in
https://lgtm.com/projects/g/apache/poi/alerts/?mode=list and in FindBugs output
(see the spike in https://builds.apache.org/view/P/vi
On Fri, 19 Oct 2018, Nick Burch wrote:
The immediate change would be:
* Everything at https://poi.apache.org/apidocs/ gets pushed to
https://poi.apache.org/apidocs/dev/
* A new page at https://poi.apache.org/apidocs/ which says which
versions you can see javadocs for online, and instructions
+1 for next weekend/week as well.
Liking the current state of things after the initial 4.0.0 public feedback.
On Tue, Oct 30, 2018 at 8:31 AM Alain FAGOT BÉAREZ
wrote:
> +1 to release 4.0.1
>
> The blocking issues related to charts in XDDF are now fixed. Related
> Bugzilla issue has also been r
+1 to release 4.0.1
The blocking issues related to charts in XDDF are now fixed. Related Bugzilla
issue has also been resolved.
Some tricks from StackOverflow tickets have been integrated into the code base
and in the examples. Some Bugzilla issues were resolved as side effect.
Remaining chart
https://bz.apache.org/bugzilla/show_bug.cgi?id=62625
Tim Allison changed:
What|Removed |Added
Summary|Regression in |VBAMacroReader in
|VBA
https://bz.apache.org/bugzilla/show_bug.cgi?id=62625
--- Comment #3 from Tim Allison ---
To clarify, this wasn't a regression. This was a bug that became apparent with
better exception handling.
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bz.apache.org/bugzilla/show_bug.cgi?id=62869
Bug ID: 62869
Summary: Let's add the VBAMacroReader to our integration tests
Product: POI
Version: unspecified
Hardware: PC
Status: NEW
Severity: enhancement
https://bz.apache.org/bugzilla/show_bug.cgi?id=62625
Tim Allison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
+1 "end of this week" that'll work well for my issues, too. I want to
confirm I didn't break anything in my recent commits via large scale
regression testing.
On Tue, Oct 30, 2018 at 8:31 AM Yegor Kozlov wrote:
>
> +1
>
> Bug 62836 is pending. I'm going to check in the code anyway, just waiting
>
+1
Bug 62836 is pending. I'm going to check in the code anyway, just waiting
to see if the contributor is planning any follow-up patches. Please give me
time till the end of this week.
Yegor
On Tue, Oct 30, 2018 at 10:59 AM pj.fanning wrote:
> Is it time for us to look at doing a POI 4.0.1 rel
+1 for rolling it out soon
I think the grace period is over and we can go on rolling the fixes out.
Also my (H)EMF implementation is giving promising results and although EMF+
is not yet implemented, I think the slideshow users, would benefit from it
... but I don't want to spoil the bugfix releas
Is it time for us to look at doing a POI 4.0.1 release?
Are there any issues we would like to see completed before we proceed?
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mai
15 matches
Mail list logo