poi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 59907] HSSFClientAnchor.setAnchorType API was broken (problem with jasperreports-5.1.0 and poi-3.14)
Date Wed, 14 Sep 2016 02:52:50 GMT

Javen O'Neal <onealj@apache.org> changed:

           What    |Removed                     |Added
          Component|HSSF                        |SS Common

--- Comment #8 from Javen O'Neal <onealj@apache.org> ---
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-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org

View raw message