xawt??

Phil Race philip.race at oracle.com
Thu May 16 09:57:03 PDT 2013


Artem,

Is http://bugs.sun.com/view_bug.do?bug_id=8001338
[macosx] -Dawt.toolkit=sun.awt.X11.XToolkit option does not work

considered to be the right bug to track this, since the last comment is

"I think that we should not support XToolkit on Mac OS X." ?

-phil.

On 5/16/2013 8:58 AM, Artem Ananiev wrote:
>
> On 5/16/2013 7:36 PM, David DeHaven wrote:
>>
>> I found about four issues pertaining to this particular problem 
>> (including the one I'm working on). I think ideally, it should be a 
>> configure switch so if someone wants to build it then they can, but 
>> for production purposes it should be off.
>>
>> I was hoping to fix jawt_md.h for 7u40 though...
>
> Such a change as removing XAWT should be done in major releases. When 
> a component becomes obsolete, it is first made non-default, then 
> deprecated in the next major release, then removed in the next next 
> major release. This is what we did for MToolkit, for example.
>
> So let us get rid of XAWT in JDK8, not 7uX.
>
> Thanks,
>
> Artem
>
>> -DrD-
>>
>>> Hi, David.
>>> Yes there is a bug on it for jdk8. The reason why it is exists, is 
>>> used for comparing of a rendering of aqua/xawt.
>>>
>>> On 16.05.2013 3:12, David DeHaven wrote:
>>>> Is there any particular reason xawt (and awt/X11) is being built on 
>>>> Mac?
>>>> Is anyone actually using it or is this just some vestige of the 
>>>> initial port that wasn't shut off?
>>>>
>>>> To me it just looks like a whole mass of dead code wasting space in 
>>>> the JRE.
>>>>
>>>> More importantly, it's getting in the way of fixing the Mac OS X 
>>>> jawt_md.h so it's actually usable...
>>>>
>>>> -DrD-
>>>>
>>>
>>>
>>> -- 
>>> Best regards, Sergey.
>>>
>>



More information about the macosx-port-dev mailing list