* Alex Kasko <m...@alexkasko.com> [2014-04-19 14:26]: > I noticed changes in AWT code and some of them seem like > Windows-only. What is the reasoning behind porting Windows changes > like these ones [1, 2] ? As I understand, windows changes themselves > kind of unintended. Maybe they contain changes to shared code that > will be used in Linux and the Windows-specific changes are ported > just as parts of the commits?
Andrew Hughes might be in a better position to answer what happened in this case. In general, the security patches are taken from 7u and sometimes don't apply to 6 as is. So we backport additional patches until the security patches apply. The Windows patches don't get any special treatment; we just backport whatever is needed until the security patches apply properly. > I am trying to build it on Windows and these AWT changes have some > discrepancies. Windows AWT code in jdk7 was changed heavily and it's > hard to make these "partly-backported" version compilable. Could you > please advise me, what is the better way to fix this - I can either > try to backport more required AWT changes from jdk7 or to revert > some of these changes from jdk6? In the interest of longer-term maintenance, I think it's better to get closer to 7 rather than further away from it. I would strongly recommend backporting additional changes from jdk7 to jdk6. If you can point me to the patches, I can include them in jdk6. Thanks, Omair -- PGP Key: 66484681 (http://pgp.mit.edu/) Fingerprint = F072 555B 0A17 3957 4E95 0056 F286 F14F 6648 4681