JDK-8186549 : move ExtendedRobot closer to tests
  • Type: Sub-task
  • Component: client-libs
  • Affected Version: 10
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-08-21
  • Updated: 2018-12-06
  • Resolved: 2018-11-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 12
12 b23Fixed
Related Reports
Relates :  
JDK-8214943 - PIT: javax/swing/JFrame/NSTexturedJFrame/NSTexturedJFrame.java errors out in mac
Relates :  
JDK-8214470 - PIT: javax/swing/JPopupMenu/7154841/bug7154841.java errors out on mac10.13
Description
ExtendedRobot testlibrary class is used by javax/swing and java/awt tests only, it's not generic enough to be a part of common testlibrary, hence it might be a good idea to move it closer to the tests which use it
Comments
test/jdk/lib/client looks like a good location
18-09-2018
in this case, I think we should leave ExtendedRobot somewhere in open/test/jdk/lib, e.g. open/test/jdk/lib/client/, and also put it in a package, e.g. jdk.test.client.lib.
21-11-2017
There are 301 usages in java/awt and 41 in javax/swing. Moving this class in either directory is asymmetrical. Perhaps there could be a sub-directory for client libs within the common test libraries dir?
21-11-2017
moving back to client-lib, ExtendedRobot is used only by client tests.
20-11-2017