Specify mapUri for directories

pkg/analysis_server/tool/spec/spec_input.html

Index: pkg/analysis_server/tool/spec/spec_input.html
diff --git a/pkg/analysis_server/tool/spec/spec_input.html b/pkg/analysis_server/tool/spec/spec_input.html
index 562b853e3ee57ac15039f3fb5a23220943ee5fad..407ec9ae05c110db869784ff634dd69ed4697f36 100644
--- a/pkg/analysis_server/tool/spec/spec_input.html
+++ b/pkg/analysis_server/tool/spec/spec_input.html
@@ -394,8 +394,8 @@
                 </value>
               </map>
               <p>
-                A mapping from context source roots to package maps which map 
-                package names to source directories for use in client-side 
+                A mapping from context source roots to package maps which map
+                package names to source directories for use in client-side
                 package URI resolution.
               </p>
             </field>
@@ -1657,6 +1657,11 @@
         <p>
           Exactly one of the file and uri fields must be provided.
         </p>
+        <p>
+          If the root of the execution context is a directory rather than a

[scheglov, 2015/02/02 18:17:52]

What is "the root of the execution context"?
Is it defined somewhere?

"createContext" says "execution context for the executable file with the given
path", it does not mention root or folders.

[Paul Berry, 2015/02/02 19:07:58]

I'm not terribly familiar with this part of the API, so hopefully the questions
below will make sense:

Do you perhaps mean something like "if the file or uri parameter specifies a
path that is a directory rather than a file"?

Should we also specify what happens if the file or uri parameter specifies a
path that does not exist on the filesystem?

+          file, then an error of type <tt>MAP_URI_FOR_DIRECTORY</tt> will be
+          generated.
+        </p>
         <params>
           <field name="id">
             <ref>ExecutionContextId</ref>