Pavel Pervov wrote:
IMHO it would be good for classlib to move to pure icu4j for the reasons
I've stated, plus it would mean that we could entirely remove the native
code from the text module and also the BidiWrapper class, which I see as
a bonus.
I do not object here. :)
There are still a few bugs to be ironed out in icu4j 3.8 before we start
using it (unless we are willing to put up with almost all the Bidi tests
failing, which I don't think would be acceptable) so the transition to
3.8 would not happen for a little while yet anyway. When the time came,
I would think it would make sense to move these libraries to DRLVM as
they would no longer be dependencies of classlib. Perhaps at that point
it would also be worth stepping the icu4c libraries up to 3.8 so
classlib and drlvm are at the same level?
I think when we are done with classlib, we file a JIRA on DRLVM build to
update ICU4C to the latest version and to move it to DRLVM dependencies.
Sounds like the right thing to do, thanks Pavel.
Regards,
Oliver
Regards,
Oliver
WBR,
--
Oliver Deakin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
