Nick Burch wrote:
On Fri, 18 Jul 2008, Rainer Schwarze wrote:
[...]
Since JasperReports is built against POI-3.0.1 and no rebuild of
JasperReports should be necessary, binary compatibility is needed.
I'm not sure if we have a decision on if 3.0 to 3.5 should be binary
compatible or not. Source compatible in almost all cases we've already
decided we're aiming for, but perhaps not binary.
I would expect that complete binary compatibility is not possible.
However, if adding "a few old methods" (and removing them in the next
major release) solves a certain amount of issues, its probably worth it.
However, I don't see why we can't add in the overloaded method for
common cases that people use. So, I've done it for this case, and I'm
happy for it to happen for other common ones, I just won't go looking
for them!
Thanks. Here is another case with JasperReports 3.0.0:
HSSFCellStyle.setFont([HSSF]Font)
In "my" project I added some more old interface methods to be sure, but
simple tests seem to show that adding "old" setCellStyle and setFont
should be enough.
(While testing different versions, I had troubles with POI 3.1, but this
deserves a specific bug report if I found out what is the cause.)
If the code which uses HSSF doesn't know about XSSF and only deals
with HSSF, should it still work with the 3.5 branch without
modification / rebuild?
Without modification, yes, in almost all cases. Without rebuild, see above!
Ok. Thanks for the information :-)
Best wishes, Rainer
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
