From d00cfc51fb5b6e067bf0cd31af670ad4b61d1a7d Mon Sep 17 00:00:00 2001 From: Kenny Guy Date: Thu, 18 Sep 2014 16:24:31 +0100 Subject: [PATCH] Remove suggested key names as its confusing. Update java doc to not suggest package names as it confused people into thinking it would limit access to that package which isn't the case. Bug: 15177676 Change-Id: I0736976956d8bb604e5097326c8c4316b3007d64 --- core/java/android/app/admin/DevicePolicyManager.java | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/core/java/android/app/admin/DevicePolicyManager.java b/core/java/android/app/admin/DevicePolicyManager.java index 13ed8d1f7bce5..027eb2c748168 100644 --- a/core/java/android/app/admin/DevicePolicyManager.java +++ b/core/java/android/app/admin/DevicePolicyManager.java @@ -2571,9 +2571,7 @@ public class DevicePolicyManager { * application running in the managed profile. * *

The provided {@link Bundle} consists of key-value pairs, where the types of values may be - * boolean, int, String, or String[]. The recommended format for keys - * is "com.example.packagename/example-setting" to avoid naming conflicts with library - * components such as {@link android.webkit.WebView}. + * boolean, int, String, or String[]. * *

The application restrictions are only made visible to the target application and the * profile or device owner.