[Bug 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 Javen O'Neal changed: What|Removed |Added Blocks||59836 Referenced Bugs: https://bz.apache.org/bugzilla/show_bug.cgi?id=59836 [Bug 59836] Tracker: Replace primitives with enums -- 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: [Bug 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
I was thinking the same thing. I can lead this release. On Nov 8, 2016 9:39 AM, "Nick Burch" wrote: > On Tue, 8 Nov 2016, bugzi...@apache.org wrote: > >> (HX)SSFClientAnchor.setAnchorType(int) was restored in r1760617, which >> was after the release of POI 3.15 final. This will be available again in >> POI 3.16 beta 1 and 3.16 final. >> > > Is it worth doing a 3.16 beta 1 release quite soon, so that people > affected by this (and the related) issue can easily upgrade to get the fix? > > Nick > > - > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org > For additional commands, e-mail: dev-h...@poi.apache.org > >
Re: [Bug 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
On Tue, 8 Nov 2016, bugzi...@apache.org wrote: (HX)SSFClientAnchor.setAnchorType(int) was restored in r1760617, which was after the release of POI 3.15 final. This will be available again in POI 3.16 beta 1 and 3.16 final. Is it worth doing a 3.16 beta 1 release quite soon, so that people affected by this (and the related) issue can easily upgrade to get the fix? Nick - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
[Bug 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 Javen O'Neal changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #12 from Javen O'Neal --- (HX)SSFClientAnchor.setAnchorType(int) was restored in r1760617, which was after the release of POI 3.15 final. This will be available again in POI 3.16 beta 1 and 3.16 final. -- 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 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 alexey.izmay...@netcracker.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #11 from alexey.izmay...@netcracker.com --- Hi, Can you keep both methods: new for enum and obsolete for int? setAnchorType(int) should be marked as @Deprecated and removed in next major release (not minor). -- 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 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 --- Comment #10 from Javen O'Neal --- (In reply to Javen O'Neal from comment #8) > I have opened discussion for how to handle getAnchorType() returns int or > AnchorType enum on the dev mailing list. https://lists.apache.org/thread.html/e8b4b6c5c54497d2a64b0855093569a53edddbfa6bf559a10a10ddb1@ https://lists.apache.org/thread.html/f7a862484826f01bdd3c8a8c82e143ec02c434bce916d3495c48ae8b@ -- 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 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 Javen O'Neal changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED -- 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 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 --- Comment #9 from Javen O'Neal --- Because this regression was accidentally included in 3.15 final, we will leave this backwards breaking change in, rather than breathing another release to revert Tue behavior. Please upgrade your Jasper reports code to use enums. -- 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 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 Dominik Stadler changed: What|Removed |Added Severity|critical|regression -- 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 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 Javen O'Neal changed: What|Removed |Added Component|HSSF|SS Common --- Comment #8 from Javen O'Neal --- This affects both HSSF and XSSF. In r1760617, I have restored ClientAnchor#setAnchorType(int) to regain backwards compatibility with POI 3.13 that was broken in POI 3.14 beta 1 thru POI 3.15 final RC2. ClientAnchor#setAnchorType(int) will be available in 3.15 final RC3 and removed no earlier than 3.17. I have opened discussion for how to handle getAnchorType() returns int or AnchorType enum on the dev mailing list. Reverting back to 3.13's behavior of returning an int would break backwards compatibility for those who upgraded to 3.14, and break compatibility when we switch to only supporting enums. Assuming Jasper Reports does not call AnchorType.getAnchorType(), the commit mentioned above should fix your problem from comment 1. -- 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 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 alexey.izmay...@netcracker.com changed: What|Removed |Added Summary|problem with|HSSFClientAnchor.setAnchorT |jasperreports-5.1.0 and |ype API was broken (problem |poi-3.14|with jasperreports-5.1.0 ||and poi-3.14) -- 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 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
https://bz.apache.org/bugzilla/show_bug.cgi?id=59907 alexey.izmay...@netcracker.com changed: What|Removed |Added OS|Mac OS X 10.1 |All -- 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
