Remove DirectoryException and LinkException from dart:io and use FileException instaed.

sdk/lib/io/file_system_entity.dart

 // Copyright (c) 2013, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 part of dart.io;
 
 class FileSystemEntityType {
   static const FILE = const FileSystemEntityType._internal(0);
   static const DIRECTORY = const FileSystemEntityType._internal(1);
   static const LINK = const FileSystemEntityType._internal(2);
@@ skipping 207 matching lines @@
   /**
    * Resolves the path of a file system object relative to the
    * current working directory, resolving all symbolic links on
    * the path and resolving all '..' and '.' path segments.
    * [resolveSymbolicLinks] returns a [:Future<String>:]
    *
    * [resolveSymbolicLinks] uses the operating system's native filesystem api
    * to resolve the path, using the realpath function on linux and
    * Mac OS, and the GetFinalPathNameByHandle function on Windows.
    * If the path does not point to an existing file system object,
-   * [resolveSymbolicLinks] completes the returned Future with an FileException.
+   * [resolveSymbolicLinks] completes the returned Future with an FileSystemException.
    *
    * On Windows, symbolic links are resolved to their target before applying
    * a '..' that follows, and on other platforms, the '..' is applied to the
    * symbolic link without resolving it.  The second behavior can be emulated
    * on Windows by processing any '..' segments before calling
    * [resolveSymbolicLinks].  One way of doing this is with the URI class:
    * [:new Uri.parse('.').resolveUri(new Uri.file(input)).toFilePath();],
    * since [resolve] removes '..' segments.
    */
   Future<String> resolveSymbolicLinks() {
@@ skipping 10 matching lines @@
 
   /**
    * Resolves the path of a file system object relative to the
    * current working directory, resolving all symbolic links on
    * the path and resolving all '..' and '.' path segments.
    *
    * [resolveSymbolicLinksSync] uses the operating system's native
    * filesystem api to resolve the path, using the realpath function
    * on linux and Mac OS, and the GetFinalPathNameByHandle function on Windows.
    * If the path does not point to an existing file system object,
-   * [resolveSymbolicLinksSync] throws a FileException.
+   * [resolveSymbolicLinksSync] throws a FileSystemException.
    *
    * On Windows, symbolic links are resolved to their target before applying
    * a '..' that follows, and on other platforms, the '..' is applied to the
    * symbolic link without resolving it.  The second behavior can be emulated
    * on Windows by processing any '..' segments before calling
    * [resolveSymbolicLinks].  One way of doing this is with the URI class:
    * [:new Uri.parse('.').resolveUri(new Uri.file(input)).toFilePath();],
    * since [resolve] removes '..' segments.
    */
   String resolveSymbolicLinksSync() {
@@ skipping 315 matching lines @@
       .then((response) {
         if (_isErrorResponse(response)) {
           throw _exceptionFromResponse(response, "Error getting type", path);
         }
         return response;
       });
   }
 
   static _throwIfError(Object result, String msg, [String path]) {
     if (result is OSError) {
-      throw new FileException(msg, path, result);
+      throw new FileSystemException(msg, path, result);
     } else if (result is ArgumentError) {
       throw result;
     }
   }
 
   static String _trimTrailingPathSeparators(String path) {
     // Don't handle argument errors here.
     if (path is! String) return path;
     if (Platform.operatingSystem == 'windows') {
       while (path.length > 1 &&
@@ skipping 101 matching lines @@
   }
 }
 
 
 abstract class _FileSystemWatcher {
   external factory _FileSystemWatcher(String path, int events, bool recursive);
   external static bool get isSupported;
 
   Stream<FileSystemEvent> get stream;
 }