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..e3a869e88d54faa5494908395f57b3245877bee6 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,24 @@
         <p>
           Exactly one of the file and uri fields must be provided.
         </p>
+        <p>
+          If the file field is provided and the value is not the path of a file
+          (either the file does not exist or the path references something other
+          than a file), then an error of type <tt>MAP_URI_INVALID_FILE</tt> will
+          be generated.
+        </p>
+        <p>
+          If the uri field is provided and the value is not a valid URI or if
+          the URI references something that is not a file (either a file that
+          does not exist or something other than a file), then an error of type
+          <tt>MAP_URI_INVALID_URI</tt> will be generated.
+        </p>
+        <p>
+          If the contextRoot used to create the execution context is not a file
+          (either the file does not exist or the path references something other
+          than a file), then an error of type <tt>INVALID_EXECUTION_CONTEXT</tt>
+          will be generated.

[scheglov, 2015/02/02 20:35:43]

Why not generate this error in response to execution.createContext ?

But yes, in "mapUri" it is still an error to pass an invalid "id".

[Brian Wilkerson, 2015/02/02 20:44:03]

The presence or absence of the resource, as well as the kind of the resource,
can change between the time createContext is sent and the time this request is
sent. That means we need to deal with it here in any case. It it therefore more
consistent with the rest of the API's design to ignore it at creation time and
deal with the problem at use time (see analysis.setAnalysisRoots for an
example).

[scheglov, 2015/02/02 20:47:04]

Right.
Thank you for explaining this!

+        </p>
         <params>
           <field name="id">
             <ref>ExecutionContextId</ref>