You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Oliver Deakin <ol...@googlemail.com> on 2007/10/25 12:35:11 UTC
[classlib] Moving to ICU4J 3.8
Since there have been no objections, I will commit my changes to move
classlib to icu4j 3.8.
I will leave the icu4c and icu4jni 3.4.4 libraries intact for the time
being, as they are currently needed by both drlvm and J9. Even though
these libraries will still be copied into the jre/bin directory by the
classlib build process, they will no longer be used by classlib. I will
be checking in an updated version of icu4j 3.8 jar from a recent
checkout of the icu code - this is because there are some bug fixes we
require that are not in the current 3.8 release. Once 3.8.1 is made
available, I will alter the build process to automatically download that
instead.
I am also removing the text module native code, as this is no longer needed.
It would be great if everyone could take a look and test these changes,
especially with drlvm and the federated build. Please let me know if
there is anything I have overlooked or if there are any other issues.
Regards,
Oliver
--
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
Re: [classlib] Moving to ICU4J 3.8
Posted by Oliver Deakin <ol...@googlemail.com>.
Yes, definitely - thanks Mark.
Regards,
Oliver
Mark Hindess wrote:
> At the very least I assume we'll want to remove the hytext entry from
> the api_dll_files list in vm/vmcore/src/init/vm_properties.cpp?
>
> -Mark.
>
> On 25 October 2007 at 15:07, "Alexei Zakharov" <al...@gmail.com> wrote:
>
>> Hi Oliver,
>>
>> Thanks for doing this. However, does this affect Harmony-specific
>> charset providers somehow? I didn't understand this from your message.
>>
>> Thanks,
>> Alexei
>>
>> 2007/10/25, Oliver Deakin <ol...@googlemail.com>:
>>
>>> Since there have been no objections, I will commit my changes to move
>>> classlib to icu4j 3.8.
>>>
>>> I will leave the icu4c and icu4jni 3.4.4 libraries intact for the time
>>> being, as they are currently needed by both drlvm and J9. Even though
>>> these libraries will still be copied into the jre/bin directory by the
>>> classlib build process, they will no longer be used by classlib. I will
>>> be checking in an updated version of icu4j 3.8 jar from a recent
>>> checkout of the icu code - this is because there are some bug fixes we
>>> require that are not in the current 3.8 release. Once 3.8.1 is made
>>> available, I will alter the build process to automatically download that
>>> instead.
>>>
>>> I am also removing the text module native code, as this is no longer needed
>>>
>> .
>>
>>> It would be great if everyone could take a look and test these changes,
>>> especially with drlvm and the federated build. Please let me know if
>>> there is anything I have overlooked or if there are any other issues.
>>>
>>> Regards,
>>> Oliver
>>>
>>> --
>>> Oliver Deakin
>>> Unless stated otherwise above:
>>> IBM United Kingdom Limited - Registered in England and Wales with number 74
>>>
>> 1598.
>>
>>> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
>>>
>>>
>>>
>
>
>
>
--
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
Re: [classlib] Moving to ICU4J 3.8
Posted by Mark Hindess <ma...@googlemail.com>.
At the very least I assume we'll want to remove the hytext entry from
the api_dll_files list in vm/vmcore/src/init/vm_properties.cpp?
-Mark.
On 25 October 2007 at 15:07, "Alexei Zakharov" <al...@gmail.com> wrote:
> Hi Oliver,
>
> Thanks for doing this. However, does this affect Harmony-specific
> charset providers somehow? I didn't understand this from your message.
>
> Thanks,
> Alexei
>
> 2007/10/25, Oliver Deakin <ol...@googlemail.com>:
> > Since there have been no objections, I will commit my changes to move
> > classlib to icu4j 3.8.
> >
> > I will leave the icu4c and icu4jni 3.4.4 libraries intact for the time
> > being, as they are currently needed by both drlvm and J9. Even though
> > these libraries will still be copied into the jre/bin directory by the
> > classlib build process, they will no longer be used by classlib. I will
> > be checking in an updated version of icu4j 3.8 jar from a recent
> > checkout of the icu code - this is because there are some bug fixes we
> > require that are not in the current 3.8 release. Once 3.8.1 is made
> > available, I will alter the build process to automatically download that
> > instead.
> >
> > I am also removing the text module native code, as this is no longer needed
> .
> >
> > It would be great if everyone could take a look and test these changes,
> > especially with drlvm and the federated build. Please let me know if
> > there is anything I have overlooked or if there are any other issues.
> >
> > Regards,
> > Oliver
> >
> > --
> > Oliver Deakin
> > Unless stated otherwise above:
> > IBM United Kingdom Limited - Registered in England and Wales with number 74
> 1598.
> > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
> >
> >
>
Re: [classlib] Moving to ICU4J 3.8
Posted by Oliver Deakin <ol...@googlemail.com>.
Hi Alexei,
This should not affect the Harmony charset providers - it is basically a
straight replacement for icu4c/jni with icu4j and does not alter use of
internal charsets.
Regards,
Oliver
Alexei Zakharov wrote:
> Hi Oliver,
>
> Thanks for doing this. However, does this affect Harmony-specific
> charset providers somehow? I didn't understand this from your message.
>
> Thanks,
> Alexei
>
> 2007/10/25, Oliver Deakin <ol...@googlemail.com>:
>
>> Since there have been no objections, I will commit my changes to move
>> classlib to icu4j 3.8.
>>
>> I will leave the icu4c and icu4jni 3.4.4 libraries intact for the time
>> being, as they are currently needed by both drlvm and J9. Even though
>> these libraries will still be copied into the jre/bin directory by the
>> classlib build process, they will no longer be used by classlib. I will
>> be checking in an updated version of icu4j 3.8 jar from a recent
>> checkout of the icu code - this is because there are some bug fixes we
>> require that are not in the current 3.8 release. Once 3.8.1 is made
>> available, I will alter the build process to automatically download that
>> instead.
>>
>> I am also removing the text module native code, as this is no longer needed.
>>
>> It would be great if everyone could take a look and test these changes,
>> especially with drlvm and the federated build. Please let me know if
>> there is anything I have overlooked or if there are any other issues.
>>
>> Regards,
>> Oliver
>>
>> --
>> 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
>>
>>
>>
>
>
--
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
Re: [classlib] Moving to ICU4J 3.8
Posted by Alexei Zakharov <al...@gmail.com>.
Hi Oliver,
Thanks for doing this. However, does this affect Harmony-specific
charset providers somehow? I didn't understand this from your message.
Thanks,
Alexei
2007/10/25, Oliver Deakin <ol...@googlemail.com>:
> Since there have been no objections, I will commit my changes to move
> classlib to icu4j 3.8.
>
> I will leave the icu4c and icu4jni 3.4.4 libraries intact for the time
> being, as they are currently needed by both drlvm and J9. Even though
> these libraries will still be copied into the jre/bin directory by the
> classlib build process, they will no longer be used by classlib. I will
> be checking in an updated version of icu4j 3.8 jar from a recent
> checkout of the icu code - this is because there are some bug fixes we
> require that are not in the current 3.8 release. Once 3.8.1 is made
> available, I will alter the build process to automatically download that
> instead.
>
> I am also removing the text module native code, as this is no longer needed.
>
> It would be great if everyone could take a look and test these changes,
> especially with drlvm and the federated build. Please let me know if
> there is anything I have overlooked or if there are any other issues.
>
> Regards,
> Oliver
>
> --
> 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
>
>
Re: [classlib] Moving to ICU4J 3.8
Posted by Oliver Deakin <ol...@googlemail.com>.
Great - thanks for checking Gregory!
Regards,
Oliver
Gregory Shimansky wrote:
> Oliver Deakin wrote:
>> Since there have been no objections, I will commit my changes to move
>> classlib to icu4j 3.8.
>>
>> I will leave the icu4c and icu4jni 3.4.4 libraries intact for the
>> time being, as they are currently needed by both drlvm and J9. Even
>> though these libraries will still be copied into the jre/bin
>> directory by the classlib build process, they will no longer be used
>> by classlib. I will be checking in an updated version of icu4j 3.8
>> jar from a recent checkout of the icu code - this is because there
>> are some bug fixes we require that are not in the current 3.8
>> release. Once 3.8.1 is made available, I will alter the build process
>> to automatically download that instead.
>>
>> I am also removing the text module native code, as this is no longer
>> needed.
>>
>> It would be great if everyone could take a look and test these
>> changes, especially with drlvm and the federated build. Please let me
>> know if there is anything I have overlooked or if there are any other
>> issues.
>
> I took a look, well, in fact fixed DRLVM that had hardcoded preload
> for hytext in the code. This one line fix (588218) made it work again.
> So far I didn't notice any other problems with running drlvm.
>
--
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
Re: [classlib] Moving to ICU4J 3.8
Posted by Gregory Shimansky <gs...@apache.org>.
Oliver Deakin wrote:
> Since there have been no objections, I will commit my changes to move
> classlib to icu4j 3.8.
>
> I will leave the icu4c and icu4jni 3.4.4 libraries intact for the time
> being, as they are currently needed by both drlvm and J9. Even though
> these libraries will still be copied into the jre/bin directory by the
> classlib build process, they will no longer be used by classlib. I will
> be checking in an updated version of icu4j 3.8 jar from a recent
> checkout of the icu code - this is because there are some bug fixes we
> require that are not in the current 3.8 release. Once 3.8.1 is made
> available, I will alter the build process to automatically download that
> instead.
>
> I am also removing the text module native code, as this is no longer
> needed.
>
> It would be great if everyone could take a look and test these changes,
> especially with drlvm and the federated build. Please let me know if
> there is anything I have overlooked or if there are any other issues.
I took a look, well, in fact fixed DRLVM that had hardcoded preload for
hytext in the code. This one line fix (588218) made it work again. So
far I didn't notice any other problems with running drlvm.
--
Gregory