Initial commit.

Author: nex3

.analysis_options

@@ -0,0 +1,2 @@
+analyzer:
+  strong-mode: true

.gitignore

@@ -0,0 +1,9 @@
+.buildlog
+.DS_Store
+.idea
+.pub/
+.settings/
+build/
+packages
+.packages
+pubspec.lock

.test_config

@@ -0,0 +1,5 @@
+{ 
+  "test_package": {
+    "platforms": ["vm"]
+  }
+}

AUTHORS

@@ -0,0 +1,6 @@
+# Below is a list of people and organizations that have contributed
+# to the project. Names should be added to the list like so:
+#
+#   Name/Organization <email address>
+
+Google Inc.

CHANGELOG.md

@@ -0,0 +1,3 @@
+## 1.0.0
+
+* Initial version.

CONTRIBUTING.md

@@ -0,0 +1,33 @@
+Want to contribute? Great! First, read this page (including the small print at
+the end).
+
+### Before you contribute
+Before we can use your code, you must sign the
+[Google Individual Contributor License Agreement](https://cla.developers.google.com/about/google-individual)
+(CLA), which you can do online. The CLA is necessary mainly because you own the
+copyright to your changes, even after your contribution becomes part of our
+codebase, so we need your permission to use and distribute your code. We also
+need to be sure of various other things—for instance that you'll tell us if you
+know that your code infringes on other people's patents. You don't have to sign
+the CLA until after you've submitted your code for review and a member has
+approved it, but you must do it before we can put your code into our codebase.
+
+Before you start working on a larger contribution, you should get in touch with
+us first through the issue tracker with your idea so that we can help out and
+possibly guide you. Coordinating up front makes it much easier to avoid
+frustration later on.
+
+### Code reviews
+All submissions, including submissions by project members, require review.
+
+### File headers
+All files in the project must start with the following header.
+
+    // Copyright (c) 2015, 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.
+
+### The small print
+Contributions made by corporations are covered by a different agreement than the
+one above, the
+[Software Grant and Corporate Contributor License Agreement](https://developers.google.com/open-source/cla/corporate).

LICENSE

@@ -0,0 +1,26 @@
+Copyright 2015, the Dart project authors. All rights reserved.
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
+met:
+
+    * Redistributions of source code must retain the above copyright
+      notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above
+      copyright notice, this list of conditions and the following
+      disclaimer in the documentation and/or other materials provided
+      with the distribution.
+    * Neither the name of Google Inc. nor the names of its
+      contributors may be used to endorse or promote products derived
+      from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

README.md

@@ -0,0 +1,20 @@
+A package that defines a common class, [`PackageResolver`][PackageResolver], for
+defining how to resolve `package:` URIs. This class may be based on the current
+isolate's package resolution strategy, but it may also be explicitly defined by
+the user—for example, you could create a resolver that represents the strategy
+used to compile a `.dart.js` file.
+
+[PackageResolver]: https://www.dartdocs.org/documentation/package_resolver/latest/package_resolver/PackageResolver-class.html
+
+The Dart VM provides two mutually exclusive means of resolving `package:` URIs:
+a **package spec** and a **package root**.
+
+* A package spec usually comes in the form of a `.packages` file on the
+  filesystem. It defines an individual root URL for each package name, so that
+  `package:$name/$path` resolves to `$root/$path`.
+
+* A package root is a single URL that acts as the base for all `package:` URIs,
+  so that `package:$name/$path` resolves to `$base/$name/$path`.
+
+This normalizes access to these resolution schemes, and makes it easy for code
+to resolve package URIs no matter where the resolution information comes from.

codereview.settings

@@ -0,0 +1,3 @@
+CODE_REVIEW_SERVER: http://codereview.chromium.org/
+VIEW_VC: https://github.com/dart-lang/package_resolver/commit/
+CC_LIST: [email protected]

pubspec.yaml

@@ -0,0 +1,11 @@
+name: package_resolver
+version: 1.0.0
+description: First-class package resolution strategy classes.
+author: Dart Team <[email protected]>
+homepage: https://github.com/dart-lang/package_resolver
+
+environment:
+  sdk: '>=1.14.0 <2.0.0'
+
+dev_dependencies:
+  test: '^0.12.0'