dart-lang/sdk
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

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

Browse Source 
Bug: https://github.com/dart-lang/sdk/issues/48272
Change-Id: Ica02829fbf9309327210e67d059d4606bb58b528
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/235282
Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
Commit-Queue: Jaime Wren <jwren@google.com>
This commit is contained in:
Jaime Wren
2022-03-04 00:02:01 +00:00
committed by Commit Bot
parent 62628e4c00
commit b63550cb85
6 changed files with 20 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
pkg/analysis_server/tool/spec/generated/java/AnalysisServer.java
+6 -6
View File
@@ -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);