-
Bug
-
Resolution: Fixed
-
P4
-
9
-
b82
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8142037 | emb-9 | Yuri Nesterenko | P4 | Resolved | Fixed | team |
JDK-8247803 | openjdk8u272 | Alex Kasko | P4 | Resolved | Fixed | b01 |
JDK-8246110 | 8u271 | Sergey Bylokhov | P4 | Resolved | Fixed | b01 |
JDK-8251684 | emb-8u271 | Yuri Nesterenko | P4 | Resolved | Fixed | team |
So far I know 3 of them, all for OS X:
com/apple/eawt/DefaultMenuBar/DefaultMenuBarTest.java
java/awt/Mouse/EnterExitEvents/FullscreenEnterEventTest.java
java/awt/SplashScreen/FullscreenAfterSplash/FullScreenAfterSplash.java
These 3 tests ask for com.apple.eawt which is not in content on non-Apple platforms. As far as I can see, tests requiring other platform-specific packages do it using reflection and don't need at-requires tag.
com/apple/eawt/DefaultMenuBar/DefaultMenuBarTest.java
java/awt/Mouse/EnterExitEvents/FullscreenEnterEventTest.java
java/awt/SplashScreen/FullscreenAfterSplash/FullScreenAfterSplash.java
These 3 tests ask for com.apple.eawt which is not in content on non-Apple platforms. As far as I can see, tests requiring other platform-specific packages do it using reflection and don't need at-requires tag.
- backported by
-
JDK-8142037 Add @requires os.family to the client tests with access to internal OS-specific API
-
- Resolved
-
-
JDK-8246110 Add @requires os.family to the client tests with access to internal OS-specific API
-
- Resolved
-
-
JDK-8247803 Add @requires os.family to the client tests with access to internal OS-specific API
-
- Resolved
-
-
JDK-8251684 Add @requires os.family to the client tests with access to internal OS-specific API
-
- Resolved
-