Change reference from .packages to .dart_tool/package_config.json in the analysis server spec_input.html

Bug: #48272
Change-Id: Ica02829fbf9309327210e67d059d4606bb58b528
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/235282
Reviewed-by: Brian Wilkerson <[email protected]>
Commit-Queue: Jaime Wren <[email protected]>

Author: jwren

pkg/analysis_server/doc/api.html

@@ -973,7 +973,8 @@ <h4>parameters:</h4><dl><dt class="field"><b>included: List&lt;<a href="#type_Fi
         </p>
         <p>
           If a package root is a file, then the analyzer
-          will behave as though that file is a ".packages" file in the
+          will behave as though that file is a
+          ".dart_tool/package_config.json" file in the
           source directory. The effect is the same as specifying the file
           as a "--packages" parameter to the Dart VM when
           executing any Dart file inside the source directory.

pkg/analysis_server/lib/protocol/protocol_generated.dart

@@ -2583,9 +2583,9 @@ class AnalysisSetAnalysisRootsParams implements RequestParams {
   /// the normal package: URI resolution mechanism.
   ///
   /// If a package root is a file, then the analyzer will behave as though that
-  /// file is a ".packages" file in the source directory. The effect is the
-  /// same as specifying the file as a "--packages" parameter to the Dart VM
-  /// when executing any Dart file inside the source directory.
+  /// file is a ".dart_tool/package_config.json" file in the source directory.
+  /// The effect is the same as specifying the file as a "--packages" parameter
+  /// to the Dart VM when executing any Dart file inside the source directory.
   ///
   /// Files in any directories that are not overridden by this mapping have
   /// their package: URI's resolved using the normal pubspec.yaml mechanism. If

pkg/analysis_server/test/integration/support/integration_test_methods.dart

@@ -500,9 +500,10 @@ abstract class IntegrationTestMixin {
   ///   the normal package: URI resolution mechanism.
   ///
   ///   If a package root is a file, then the analyzer will behave as though
-  ///   that file is a ".packages" file in the source directory. The effect is
-  ///   the same as specifying the file as a "--packages" parameter to the Dart
-  ///   VM when executing any Dart file inside the source directory.
+  ///   that file is a ".dart_tool/package_config.json" file in the source
+  ///   directory. The effect is the same as specifying the file as a
+  ///   "--packages" parameter to the Dart VM when executing any Dart file
+  ///   inside the source directory.
   ///
   ///   Files in any directories that are not overridden by this mapping have
   ///   their package: URI's resolved using the normal pubspec.yaml mechanism.

pkg/analysis_server/tool/spec/generated/java/AnalysisServer.java

@@ -216,12 +216,12 @@ public interface AnalysisServer {
    *         not be analyzed.
    * @param packageRoots A mapping from source directories to package roots that should override the
    *         normal package: URI resolution mechanism. If a package root is a file, then the analyzer
-   *         will behave as though that file is a ".packages" file in the source directory. The
-   *         effect is the same as specifying the file as a "--packages" parameter to the Dart VM
-   *         when executing any Dart file inside the source directory. Files in any directories that
-   *         are not overridden by this mapping have their package: URI's resolved using the normal
-   *         pubspec.yaml mechanism. If this field is absent, or the empty map is specified, that
-   *         indicates that the normal pubspec.yaml mechanism should always be used.
+   *         will behave as though that file is a ".dart_tool/package_config.json" file in the source
+   *         directory. The effect is the same as specifying the file as a "--packages" parameter to
+   *         the Dart VM when executing any Dart file inside the source directory. Files in any
+   *         directories that are not overridden by this mapping have their package: URI's resolved
+   *         using the normal pubspec.yaml mechanism. If this field is absent, or the empty map is
+   *         specified, that indicates that the normal pubspec.yaml mechanism should always be used.
    */
   public void analysis_setAnalysisRoots(List<String> included, List<String> excluded, Map<String, String> packageRoots);
 

pkg/analysis_server/tool/spec/spec_input.html

@@ -870,7 +870,8 @@ <h4>Options</h4>
         </p>
         <p>
           If a package root is a file, then the analyzer
-          will behave as though that file is a ".packages" file in the
+          will behave as though that file is a
+          ".dart_tool/package_config.json" file in the
           source directory. The effect is the same as specifying the file
           as a "--packages" parameter to the Dart VM when
           executing any Dart file inside the source directory.

pkg/analysis_server_client/lib/src/protocol/protocol_generated.dart

@@ -2583,9 +2583,9 @@ class AnalysisSetAnalysisRootsParams implements RequestParams {
   /// the normal package: URI resolution mechanism.
   ///
   /// If a package root is a file, then the analyzer will behave as though that
-  /// file is a ".packages" file in the source directory. The effect is the
-  /// same as specifying the file as a "--packages" parameter to the Dart VM
-  /// when executing any Dart file inside the source directory.
+  /// file is a ".dart_tool/package_config.json" file in the source directory.
+  /// The effect is the same as specifying the file as a "--packages" parameter
+  /// to the Dart VM when executing any Dart file inside the source directory.
   ///
   /// Files in any directories that are not overridden by this mapping have
   /// their package: URI's resolved using the normal pubspec.yaml mechanism. If