chef-gen-flavors 0.8.6 → 0.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: e0b26e3895493d90b9d965e5d2d208372df82043
-  data.tar.gz: 7091c3ba4bf917a179fd67bba47723da1422544a
+  metadata.gz: 4b0953fd114c2f2abb72a230b6a78bf0e020000a
+  data.tar.gz: 771448a5c60f983e57ceace57260c6e0944cdd5d
 SHA512:
-  metadata.gz: f0199d065dcf48a1e398f6624250f79af8fb0af4ebd1f6bd9b80b03952eacf77829f938ffa5b6e6f4ea0ffa9e40905ce9bd7f73273fe436ab61739b924257e38
-  data.tar.gz: 710bf0afa1023a3ac92c2ca47058d6cae9e114201f7485ac06f22724bcdbc7f53408186b64170772eade67272ae620304c2041aac5934362cbe8685ec26e527d
+  metadata.gz: af181b0de509ad3c4e1925f1cb11eee12cc55844a5178a3d0253d9e351c2453cad52494aec943efbc174434fa4c3e0e346bd2919d2789d30a8553cb159779741
+  data.tar.gz: 0968b5d2044d14bb0fcf6185a66fcc2f29bc709f49c70c224d3c7bd8fb563ea71d3db95af85a72e52478b8995d09c647a3c9ad1d8ac3a3493d6e3dd55ae247a2

data/History.md

@@ -1,5 +1,10 @@
 # Changelog for chef-gen-flavors
 
+## 0.9.0
+
+* removed ChefGen::FlavorBase (and the snippets it uses) from this distribution and moved into a separate gem: [chef-gen-flavor-base](https://github.com/jf647/chef-gen-flavor-base)
+* the new flavor base has breaking API changes (details below); flavor authors should refer to the documentation in the new distribution for details
+
 ## 0.8.6
 
 This version contains no code changes; this is a courtesy version bump

data/LICENSE

@@ -2,6 +2,8 @@
 
 Copyright 2015 Nordstrom, Inc.
 
+Copyright 2015 James FitzGibbon
+
 Licensed under the Apache License, Version 2.0 (the "License"); you may not
 use this file except in compliance with the License. You may obtain a copy
 of the License at

data/Manifest.txt

@@ -5,7 +5,6 @@ Manifest.txt
 README.md
 chef-gen-flavors.gemspec
 lib/chef_gen/flavor.rb
-lib/chef_gen/flavor_base.rb
 lib/chef_gen/flavors.rb
 lib/chef_gen/flavors/cucumber.rb
 lib/chef_gen/flavors/cucumber/bundle.rb
@@ -14,39 +13,3 @@ lib/chef_gen/flavors/cucumber/kitchen.rb
 lib/chef_gen/flavors/cucumber/knife.rb
 lib/chef_gen/flavors/cucumber/rake.rb
 lib/chef_gen/flavors/cucumber/regex.rb
-lib/chef_gen/snippet/attributes.rb
-lib/chef_gen/snippet/chef_spec.rb
-lib/chef_gen/snippet/cookbook_base.rb
-lib/chef_gen/snippet/example_file.rb
-lib/chef_gen/snippet/example_template.rb
-lib/chef_gen/snippet/git_init.rb
-lib/chef_gen/snippet/recipes.rb
-lib/chef_gen/snippet/resource_provider.rb
-lib/chef_gen/snippet/standard_ignore.rb
-lib/chef_gen/snippet/style_foodcritic.rb
-lib/chef_gen/snippet/style_rubocop.rb
-lib/chef_gen/snippet/style_tailor.rb
-lib/chef_gen/snippet/test_kitchen.rb
-lib/chef_gen/snippets.rb
-shared/snippet/attributes/attributes_default_rb.erb
-shared/snippet/chef_spec/_rspec.erb
-shared/snippet/chef_spec/spec_chef_runner_context_rb.erb
-shared/snippet/chef_spec/spec_recipes_default_spec_rb.erb
-shared/snippet/chef_spec/spec_spec_helper_rb.erb
-shared/snippet/cookbookbase/Berksfile.erb
-shared/snippet/cookbookbase/CHANGELOG_md.erb
-shared/snippet/cookbookbase/Gemfile.erb
-shared/snippet/cookbookbase/Guardfile.erb
-shared/snippet/cookbookbase/README_md.erb
-shared/snippet/cookbookbase/Rakefile.erb
-shared/snippet/cookbookbase/metadata_rb.erb
-shared/snippet/examplefile/files_default_example_conf
-shared/snippet/exampletemplate/templates_default_example_conf_erb
-shared/snippet/recipes/recipes_default_rb.erb
-shared/snippet/resourceprovider/providers_default_rb.erb
-shared/snippet/resourceprovider/resources_default_rb.erb
-shared/snippet/stylerubocop/_rubocop_yml.erb
-shared/snippet/testkitchen/_kitchen_yml.erb
-shared/snippet/testkitchen/libraries_kitchen_helper_rb
-shared/snippet/testkitchen/test_integration_default_serverspec_recipes_default_spec_rb.erb
-shared/snippet/testkitchen/test_integration_default_serverspec_spec_helper_rb.erb

data/README.md

@@ -1,16 +1,11 @@
 # chef-gen-flavors
 
-* home :: https://github.com/Nordstrom/chef-gen-flavors
+* home :: https://github.com/jf647/chef-gen-flavors
 * license :: [Apache2](http://www.apache.org/licenses/LICENSE-2.0)
 * gem version :: [![Gem Version](https://badge.fury.io/rb/chef-gen-flavors.png)](http://badge.fury.io/rb/chef-gen-flavors)
-* build status :: [![Circle CI](https://circleci.com/gh/Nordstrom/chef-gen-flavors.svg?style=svg)](https://circleci.com/gh/Nordstrom/chef-gen-flavors)
-* code climate :: [![Code Climate](https://codeclimate.com/github/Nordstrom/chef-gen-flavors/badges/gpa.svg)](https://codeclimate.com/github/Nordstrom/chef-gen-flavors)
-* docs :: [![Inline docs](http://inch-ci.org/github/nordstrom/chef-gen-flavors.svg?branch=master)](http://inch-ci.org/github/nordstrom/chef-gen-flavors)
-
-## UPCOMING API CHANGES
-
-Please see the [changelog](History.md) for details of upcoming breaking API changes in
-the 0.9.x series.
+* build status :: [![Circle CI](https://circleci.com/gh/jf647/chef-gen-flavors.svg?style=svg)](https://circleci.com/gh/jf647/chef-gen-flavors)
+* code climate :: [![Code Climate](https://codeclimate.com/github/jf647/chef-gen-flavors/badges/gpa.svg)](https://codeclimate.com/github/jf647/chef-gen-flavors)
+* docs :: [![Inline docs](http://inch-ci.org/github/jf647/chef-gen-flavors.svg?branch=master)](http://inch-ci.org/github/jf647/chef-gen-flavors)
 
 ## DESCRIPTION
 
@@ -21,19 +16,52 @@ This gem simply provides a framework; templates are provided by separate
 gems, which you can host privately for use within your organization or
 publicly for the Chef community to use.
 
-At present this is focused primarily on providing templates for generation of
-cookbooks, as this is where most organization-specific customization takes place.
-Support for the other artifacts that ChefDK can generate may work, but is not
-the focus of early releases.
+[chef-gen-flavor-base](https://github.com/jf647/chef-gen-flavor-base) is
+a base class that makes it easy to compose a flavor from reusable
+snippets of functionality, and using it is highly recommended.  Using
+chef-gen-flavors on its own is only suitable if you already have a
+template which is a copy of the skeleton provided by ChefDK.
+
+At present this is focused primarily on providing templates for
+generation of cookbooks, as this is where most organization-specific
+customization takes place. Support for the other artifacts that ChefDK
+can generate may work, but is not the focus of early releases.
+
+### BREAKING API CHANGES
+
+v0.9.0 of chef-gen-flavors is very different from chef-gen-flavors
+v0.8.x.  Flavors will need to be re-worked, and the base flavor class
+and associated snippets have been extracted to their own gem.
+
+v0.8.6 contained a warning about this change; if you are not ready to
+upgrade your flavor you can pin to this version to keep the old API.
 
 ## INSTALLATION
 
-    chef gem install chef-gen-flavors
+You should not install this gem directly; it will be installed as a
+dependency of a flavor gem.  If you are developing a flavor, declare
+this gem a dependency of your gem in your gemspec file:
 
-You will also need to install at least one plugin, which may be distributed
-via Rubygems (in which case you install using `chef gem`) or as source, in
-which case you should refer to the installation documentation that comes with
-the plugin.
+```ruby
+Gem::Specification.new do |s|
+  s.name = 'chef-gen-flavor-awesome'
+  s.add_runtime_dependency('chef-gen-flavors', ['~> 0.9'])
+  ...
+end
+```
+
+Then make bundler read your gemspec:
+
+```ruby
+source 'https://rubygems.org/'
+gemspec
+```
+
+And use bundler to install your dependencies:
+
+```bash
+$ bundle
+```
 
 ## PREREQUISITES
 
@@ -68,13 +96,6 @@ By default, this gem does not offer the built-in ChefDK template as an
 option. By setting the environment variable CHEFDK_FLAVOR, the
 option `builtin` will be offered.
 
-## TERMINOLOGY
-
-(because everything in the Chef ecosystem has to have foodie names)
-
-* Flavor - a type of template.  Provided by a plugin in the namespace `ChefGen::Flavor::`.  Flavors can be distributed as ruby gems inside or outside of your organization.
-* Snippet - a small piece of a code_generator cookbook that flavors can compose together to avoid repeating themselves.  Nominally provided by a module in the namespace `ChefGen::Snippet::`, but can be defined in any module.  chef-gen-flavors comes with several common snippets, but you can create your own and package them as standalone gems or as part of a flavor gem
-
 ## FLAVORS
 
 This gem uses [little-plugger](https://rubygems.org/gems/little-plugger) to
@@ -86,16 +107,17 @@ The plugin must define a class inside the naming hierarchy
 `ChefGen::Flavor::`. The class name should be the filename converted to
 CamelCase (e.g. `foo_bar.rb` = `FooBar`)
 
-The name of the module must not be in all caps, as little-plugger ignores
+The name of the class must not be in all caps, as little-plugger ignores
 these (assuming that they are constants).
 
-Plugins must also define a class method named `description`, which is used
-both to find the path to the file that defines the plugin and in the prompt
-displayed when more than one plugin is available.
-
 You do not have to `require` your plugin; little-plugger searches all
 installed gems for files matching the globspec.
 
+Flavor classes must also:
+
+* define a NAME constant which is the name of the flavor in lowercase
+* provide an `#add_content` method, which is responsible for copying content to the temporary directory created by chef-gen-flavors
+
 ## EXAMPLE FLAVOR STRUCTURE
 
 This example defines a flavor named `Example`. It can only generate
@@ -107,278 +129,60 @@ A functional copy of this plugin is available on rubygems as
 The directory structure of a plugin looks like this:
 
     chef-gen-flavor-example
-    ├── code_generator
-    │   ├── files
-    │   │   └── default
-    │   ├── metadata.rb
-    │   ├── recipes
-    │   │   └── cookbook.rb
-    │   └── templates
-    │       └── default
-    └── lib
-        └── chef_gen
-            └── flavor
-                └── example.rb
-
-It is important that the name of the directory in which your generator
-cookbook lives matches the name in metadata.rb.  ChefDK uses the last
-element of the path as the cookbook name, so if you put your cookbook
-in a folder called 'cookbook' but your metadata.rb declares the name
-as 'code_generator', ChefDK won't be able to find your recipe.
-
-## ALTERNATE code_generator PATHS
-
-By default, the code_generator cookbook is assumed to live in a directory
-named `code_generator` four levels higher than the path of the file
-definining the plugin.
-
-To specify that the code_generator cookbook lives elsewhere, define a class
-method named `code_generator_path` which takes one argument (the path to the
-plugin class) and returns the path to the code_generator cookbook. If the
-`Example` plugin wanted to place the code_generator cookbook in a directory
-named `template` instead of `code_generator`, it would define an instance
-method like this:
-
-    module ChefGen
-      module Flavor
-        class Example
-          class << self
-            def description
-              'example cookbook template'
-            end
-
-            def code_generator_path(classfile)
-              File.expand_path(
-                File.join(
-                  classfile,
-                  '..', '..', '..', '..',
-                  'template'
-                )
-              )
-            end
-          end
-        end
-      end
-    end
-
-For compatibility with all platforms supported by ChefDK, plugins should use
-the methods in the `File` class to construct relative paths rather than
-assuming what the path separator should be.
-
-## GENERATOR PATH COPY
-
-When #path is called, chef-gen-flavors makes a copy of the selected
-generator cookbook to a temporary path, which is what gets returned
-and used by ChefDK.  This path is cleaned up at exit unless the environment
-variable CHEFGEN_NOCLEANTMP is set.
-
-## ADDING CONTENT TO THE GENERATOR COPY
-
-After the generator is copied to a temporary path, the #add_content
-instance method is called (if it exists) on the flavor class.  It is
-passed one arg: the path to the temporary copy.
-
-This allows flavors to create content dynamically by writing files
-to the proper directly.  It is exploited by the flavor base class
-described below.
-
-## FLAVOR BASE CLASS
-
-Inside of your plugin's code_generator cookbook, you can do anything that
-chef-solo can do. If you aren't familiar with the mechanics of the default
-generators that comes with chef-dk, you should study [those
-recipes](https://github.com/chef/chef-dk/tree/0.5.1/lib/chef-dk/skeletons/code_generator)
-first before attempting to create your own.
-
-To make the job of authoring a custom template easier, this gem comes with a
-base class that plugins can inherit from. This provides some useful
-features:
-
-* helpers to create directories and render files and templates using simple name translation
-* the ability to create and use snippets that set up commonly used functionality (i.e. ChefSpec or Test Kitchen)
-* the ability to prevent files from being overwritten when a template is being applied overtop an existing cookbook
-
-To use the base class, make it a dependency of your gem and inherit from it:
-
-    require 'chef_gen/flavor_base'
-
-    module ChefGen
-      module Flavor
-        class Amazing < FlavorBase
-        end
+    ├── lib
+    │   └── chef_gen
+    │       └── flavor
+    │           └── example.rb
+    └── shared
+        └── flavor
+            └── example
+                ├── metadata.rb
+                └── recipes
+                    └── cookbook.rb
+
+It is important that the name of the flavor matches the name in
+metadata.rb.  ChefDK uses the last element of the path as the cookbook
+name, so if you put your cookbook in a folder called 'cookbook' but your
+metadata.rb declares the name as 'example', ChefDK won't be able
+to find your recipe.
+
+## COPYING CONTENT
+
+When #path is called, chef-gen-flavors creates a temporary directory,
+which is passes as an argument to the flavor class' constructor:
+
+```ruby
+class ChefGen
+  module Flavor
+    class Awesome
+      NAME = 'awesome'
+
+      def initialize(temp_path:)
+        @temp_path = temp_path
       end
     end
-
-Then in one of your generator recipes like `recipes/cookbook.rb`, create
-an instance of your plugin, passing the recipe into which resources will
-be injected:
-
-    template = ChefGen::Flavor::Amazing.new(self)
-
-The plugin has several helper methods you can use:
-
-* `target_path` returns the full path to the target directory
-* `directories` is a `Array` of directories to create
-* `files` is an `Array` of files to create
-* `files_if_missing` is an `Array` of files to create which should not be overwritten if they exist
-* `templates` is an `Array` of templates to render
-* `templates_if_missing` is an `Array` of templates to render which should not be overwritten if they exist
-* `fail_on_clobber` is a boolean accessor which causes generation to fail if any files in the `files` or `templates` arrays already exist.  Defaults to true, but can be set to false by adding `-a clobber` to the `chef generate` command line
-* `report_actions` is a boolean accessor which causes the generator to report all of the actions it took
-* `next_steps` is a message to be displayed to the user as the last thing the generator does
-
-The distinction between files that are overwritten and those that are
-created only if they do not exist allows for updating a cookbook to an
-organization-wide policy while still allowing for per-cookbook
-customization.
-
-For example, if your cookbook template has a standard Rakefile and you wish
-to add a target to it, you can do so if Rakefile is in the `files` array.
-When the generator is used on top of an existing cookbook, the Rakefile will
-be rewritten. Custom rake tasks can be placed in `.rake` files in the
-directory `lib/tasks`, which will not be overwritten.
-
-Once the template object has been set up to your satisfaction, call the
-`#generate` method, which creates the Chef resources to generate your
-target.
-
-The list of files and templates take the path to the rendered file (e.g.
-`spec/spec_helper.rb`). The source for the file or template will be
-transformed by replacing foreward slashes and dots with underscores.
-Additionally, templates have `.erb` appended to the source.
-
-This code:
-
-    template = ChefGen::Flavor::Amazing.new
-    template.files << 'spec/spec_helper.rb'
-    template.templates << '.rubocop.yml'
-    template.generate
-
-is equivalent to manually creating these resources:
-
-    file "#{cookbook_dir}/spec/spec_helper.rb" do
-      source 'spec_spec_helper_rb'
-    end
-
-    template "#{cookbook_dir}/.rubocop.yml" do
-      source '\_rubocop\_yml.erb'
-    end
-
-### TEMPLATE SNIPPETS
-
-Many templates will use common patterns, such as providing a README.md and
-CHANGELOG.md, providing the files necessary to create a ChefSpec unit
-testing suite, or the files necessary to create a Test Kitchen integration
-testing suite.
-
-Rather than have every template author create these, this gem ships with a
-number of snippets, which can be included in your plugin class like so:
-
-    require 'chef_gen/flavor'
-    require 'chef_gen/snippets'
-
-    module ChefGen
-      module Flavor
-        class Amazing < FlavorBase
-          include ChefGen::Snippet::ChefSpec
-        end
-      end
-    end
-
-Snippets can add both declarations (files and templates to be rendered)
-and content.  This reduces the amount of content that a flavor author
-has to include in their distribution.
-
-The snippets that ship with this gem are:
-
-* `CookbookBase` - sets up the basic files any cookbook needs (README, CHANGELOG, etc.)
-* `StyleFoodcritic` - sets up the files for style checking with Foodcritic
-* `StyleRubocop` - sets up the files for style checking with Rubocop
-* `StyleTailor` - sets up the files for style checking with Tailor
-* `ChefSpec` - sets up the files for basic ChefSpec unit testing
-* `TestKitchen` - sets up the files for basic Test Kitchen integration testing
-* `Recipes` - creates recipes/default.rb
-* `Attributes` - creates attributes/default.rb
-* `ExampleFile` - creates files/default/example.conf
-* `ExampleTemplate` - creates templates/default/example.conf.erb
-* `ResourceProvider` - sets up a sample LWRP resource and provider
-
-You can also create your own snippet. A snippet is simply a module that
-provides some number of public methods prefixed with `snippet\_`. Any such
-methods will be called, passing the recipe object as the only parameter when
-`#generate` is called. For example, a simplified ChefSpec snippet might look
-like this:
-
-    module ChefGen
-      module Snippet
-        module ChefSpec
-          def snippet_chefspec(recipe)
-            @directories << 'spec'
-            @directories << File.join('spec', '/recipes')
-            @files << '.rspec'
-            @files << File.join('spec', 'spec_helper.rb')
-            @files << File.join('spec', 'recipes', 'default_spec.rb')
-          end
-        end
-      end
-    end
-
-### SNIPPET INITIALIZERS
-
-Because you cannot add on to #initialize in a class when including a
-module, the FlavorBase initializer will call any public method provided
-by a snippet prefixed by `init\_`.  For example, the StandardIgnore
-snippet initializes its list of patterns:
-
-```
-# initializes the pattern arrays
-def init_standardignore_instancevars
-  @chefignore_patterns = %w(
-    .DS_Store Icon? nohup.out ehthumbs.db Thumbs.db
-    .sasscache \#* .#* *~ *.sw[az] *.bak REVISION TAGS*
-    tmtags *_flymake.* *_flymake *.tmproj .project .settings
-    mkmf.log a.out *.o *.pyc *.so *.com *.class *.dll
-    *.exe */rdoc/ .watchr  test/* features/* Procfile
-    .git */.git .gitignore .gitmodules .gitconfig .gitattributes
-    .svn */.bzr/* */.hg/*
-  )
-  @gitignore_patterns = %w(
-    Berksfile.lock *~ *# .#* \#*# .*.sw[az] *.un~
-    bin/* .bundle/*
-  )
+  end
 end
 ```
 
-### AFTER SNIPPETS HOOK
-
-After all snippets have run, the method #after_run_snippets will be run
-if defined.  This is useful to unwind or remove things in a derived
-flavor.
-
-### SNIPPET CONTENT
-
-FlavorBase provides an #add_content method to allow snippets to create
-content.  For example, the `Attributes` snippet is defined like this:
-
-```
-module ChefGen
-  module Snippet
-    module Attributes
-      def snippet_attributes_dirs(recipe)
-        @directories << 'attributes'
-      end
-
-      def snippet_attributes_files(recipe)
-        @templates_if_missing << File.join('attributes', 'default.rb')
-      end
-
-      def content_attribute_files(path)
-        copy_snippet_file(
-          File.join(
-            File.dirname(__FILE__), '..', '..', '..',
-            'shared', 'snippet', 'attributes', 'attributes_default_rb.erb'
-          ),
-          File.join(path, 'templates', 'default', 'attributes_default_rb.erb')
+The flavor is responsible for copying everything required to run
+generation to that path by defining a `#add_content` method.  For a
+simple flavor, that might be just a recursive copy:
+
+```ruby
+class ChefGen
+  module Flavor
+    class Awesome
+      ...
+      def add_content
+        FileUtils.cp_r(
+          File.expand_path(
+            File.join(
+              File.dirname(__FILE__),
+              '..', '..', '..', 'shared', 'flavor', NAME
+            )
+          ) + '/.',
+          @temp_path
         )
       end
     end
@@ -386,39 +190,16 @@ module ChefGen
 end
 ```
 
-When a flavor that includes this snippet is selected, the file
-`shared/snippet/attributes/attributes_default_rb.erb` is copied to
-the path `templates/default/attributes_default_rb.erb` in the temporary
-generator path.
-
-Look at the snippets in the `lib/chef_gen/snippet` directory and the
-[example flavor](https://github.com/Nordstrom/chef-gen-flavor-example)
-for an full demonstration of how these hooks work.
-
-### SNIPPET DOCUMENTATION
-
-Some of the snippets provide extra functionality worth calling out:
-
-#### CookbookBase
+Once the add_content method has been called, it is returned as the
+value of `chefdk.generator_cookbook`, and generation proceeds as if
+you had given `chef generate` and alternate path by passing -g.
 
-Provides several reader methods:
+This path is cleaned up at exit unless the environment
+variable `CHEFGEN_NOCLEANTMP` is set.
 
-* `cookbook_gems`, a hash of gem names to gem constraints.  Flavors and other snippets can add to this list; all the gems are rendered to a Gemfile by this snippet
-* `gem_sources`, an array of gem source URL.  This defaults to 'https://rubygems.org' and can be replaced or added onto
-* `berks_sources`, an array of Berksfile source URLs.  This defaults to 'https://supermarket.chef.io' and can be replaced or added onto
-* `rake_tasks`, a hash of task names to task content.  This allows snippets to add extra tasks to the Rakefile, which is rendered by this snippet
-* `guard_sets`, a hash of guard set names to set content.  This allows snippets to add extra tasks to the Guardfile, which is rendered by this snippet
-
-Look at the content of these snippets for a better understanding of how
-to use these methods.  For example, the ChefSpec snippet adds gems, rake
-tasks and guard sets.
-
-#### StandardIgnore
-
-Provides several reader methods:
-
-* `chefignore_patterns`, an array of patterns to write to the chefignore file
-* `gitignore_patterns`, an array of patterns to write to the .gitignore file
+When using ChefGen::FlavorBase, there are helper functions to compose
+the temporary directory from files that come from a mix of flavors and
+reusable components.
 
 ## FEATURE TESTING FLAVORS
 
@@ -431,18 +212,20 @@ access these definitions, add the following line to your
 
 For an example of how to use these steps in your features, refer to the
 reference implementation of a flavor:
-[chef-gen-flavor-example](https://github.com/Nordstrom/chef-gen-flavor-example).
+[chef-gen-flavor-example](https://github.com/jf647/chef-gen-flavor-example).
 
 Documentation for the steps themselves is in the file `ARUBA_STEPS.md`
 
 ## AUTHOR
 
-James FitzGibbon - james.i.fitzgibbon@nordstrom.com - Nordstrom, Inc.
+[James FitzGibbon](https://github.com/jf647)
 
 ## LICENSE
 
 Copyright 2015 Nordstrom, Inc.
 
+Copyright 2015 James FitzGibbon
+
 Licensed under the Apache License, Version 2.0 (the "License"); you may not
 use this file except in compliance with the License. You may obtain a copy
 of the License at