On Thu, 10 Jul 2008, Yegor Kozlov wrote:
(1) I expect the main POI jar (poi-3.5-*.jar) to be compatible with 3.1 and
earlier releases. 3.1 has just been released and I expected 3.05-beta1 to be
roughly equivalent. Unfortunately it is no so.
org.apache.poi.hssf.util.Region was moved to org.apache.poi.ss.util.Region.
For me, it meant that I had to change all the references in my code and
re-compile it.
Bah, looks like we missed one. The plan is always that when we move the
main logic from hssf to ss (for cases when the functionality is generic
and applies to both hssf and xssf), a stub class that extends the ss
version is left behind. Seems like we missed that one.
I've committed the stub version to the branch now, and I'll aim to do some
new beta artificats for a new vote shortly
This is the only issue I found. If there are more, please make sure that
existing code works with 3.5.
Please do let me know if you happen to spot any more. We hoped that the
test suite would show them up, but sometimes refactoring using eclipse can
be too helpful...
(2) It's not clear what level of conformance should users expect from
the new OOXML code. We should have a document clearly stating what is
supported and what is not.
There is some stuff in the docs on this. The aim is for the 3.5 final
release to support most things, with an explicit list of those things not
yet working. No-one has felt motivated to write a list for the beta
release, so you just need to check the code to see if something's still a
stub method or not. Hopefully someone can step forward and write such a
list before it's time for beta 2 :)
Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
