Thanks Marius for bringing up this topic.
POI is quite an old code base and I think it is safe to assume that virtually
any return type can be null and that inputs can often be null too.
If we start annotating the code, we would probably need to cover as many
methods as possible because it woul
My view is that it's been a while since we last did a release. There shouldn't
be any pressure to finish any work that is in progress but if we think the code
base is stable enough, we could release what we have and do a 5.1.0 or 6.0.0
release in the near future.
On Wednesday 2 December 20
Hi Devs,
although I still have an unfinished business with EMF/WMF raster operations, I
think this would take some more time to be resolved.
I only know from Alain that he's still working on XDDF - but maybe his work can
be included into 5.1.0.
So are we ready for the 5.0.0 release?
Best wish
Hello,
As I've been working more with POI, I frequently find myself looking at the
javadoc and source for whether or not a function can return null. I wanted
to ask, would a contribution adding nullability annotations be welcomed?
The basic idea is to annotate return values and method parameters
https://bz.apache.org/bugzilla/show_bug.cgi?id=64945
Andreas Beeker changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=64945
--- Comment #6 from Andreas Beeker ---
Created attachment 37585
--> https://bz.apache.org/bugzilla/attachment.cgi?id=37585&action=edit
Example code to link the video
I've added the source as an attachment and also to your Stackoverflow quest
https://bz.apache.org/bugzilla/show_bug.cgi?id=64950
Bug ID: 64950
Summary: about doughnutchart
Product: POI
Version: 4.1.2-FINAL
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: XWPF
