ore 0.1.2

data/.document

@@ -0,0 +1,4 @@
+-
+ChangeLog.md
+GemspecYML.md
+LICENSE.txt

data/.rspec

@@ -0,0 +1 @@
+--colour --format documentation

data/.yardopts

@@ -0,0 +1 @@
+--markup markdown --title 'Ore Documentation' --protected

data/ChangeLog.md

@@ -0,0 +1,31 @@
+### 0.1.2 / 2010-10-25
+
+* Renamed `--jeweler` to `--jeweler-tasks` in {Ore::Generator}.
+* Renamed `--ore` to `--ore-tasks` in {Ore::Generator}.
+* Fixed the `remove` task in {Ore::CLI}.
+
+### 0.1.1 / 2010-10-25
+
+* Show stopper bug fixed.
+
+### 0.1.0 / 2010-10-25
+
+* Initial release:
+  * Added {Ore::Config}.
+  * Added {Ore::Naming}.
+  * Added {Ore::DocumentFile}.
+  * Added {Ore::Versions}:
+    * Added {Ore::Versions::Version}.
+    * Added {Ore::Versions::VersionConstant}.
+    * Added {Ore::Versions::VersionFile}.
+  * Added {Ore::Project}:
+    * Added {Ore::Checks}.
+    * Added {Ore::Defaults}.
+    * Added {Ore::Settings}.
+  * Added {Ore::Specification}.
+  * Added {Ore::Template}:
+    * Added {Ore::Template::Directory}.
+    * Added {Ore::Template::Interpolations}.
+    * Added {Ore::Template::Helpers}.
+  * Added {Ore::Generator}.
+

data/GemspecYML.md

@@ -0,0 +1,252 @@
+# gemspec.yml
+
+Ore uses the `gemspec.yml` file to store all static data about a project.
+The `gemspec.yml` is a simple YAML file, which contains the same data
+that a normal Ruby `.gemspec` file would. Below is the complete listing
+of valid data that can be listed in a `gemspec.yml` file.
+
+## name
+
+The name of the project can be listed like so:
+
+    name: foo
+
+If the name is not listed, Ore will use the base-name of the project
+directory.
+
+## version
+
+The version of the project can be listed like so:
+
+    version: 0.1.0
+
+If the version is not listed, Ore will first search for a `VERSION` or
+`VERSION.yml` file in the root of the project. If Ore cannot find any
+version files, it will then search within the `lib/` directory for a
+`version.rb`. Ore can load both Ruby `VERSION` constants or `Version`
+modules that contain `MAJOR`, `MINOR`, `PATCH` and `BUILD` constants.
+
+## summary
+
+The summary of the project can be listed like so:
+
+    summary: My awesome project
+
+## description
+
+The description of the project can be listed in a variety of ways:
+
+* Single line:
+
+      description: My project, which provides various functionality.
+
+* Text block:
+
+      description:
+        My project, which provides the developer with various attributes
+        and behaviors.
+
+If the description is not listed, it will default to the `summary`.
+
+## license
+
+The license of the project can be listed like so:
+
+    license: MIT
+
+Multiple licenses can also be listed:
+
+    license:
+     - LGPL-2.1
+     - GPL-2
+
+## authors
+
+The authors of the project can be listed like so:
+
+    author: Alice
+
+If a project has more than one author, each author can be listed:
+
+    author:
+     - Alice
+     - Eve
+     - Bob
+
+## email
+
+The primary email contact for the project can be listed like so:
+
+    email: alice@example.com
+
+## date
+
+The publish date of the current version can be listed like so:
+
+    date: 2010-10-23
+
+Ore will use [Date.parse](http://rubydoc.info/docs/ruby-stdlib/1.9.2/Date.parse)
+to parse the `date` value.
+
+If the `date` is not listed, Ore will default it to the current date.
+
+## require_paths
+
+The require_paths of a project can be listed like so:
+
+    require_paths: lib
+
+If there are more than one require_path that needs listing:
+
+    require_paths:
+     - ext
+     - lib
+
+## executables
+
+The names of the executables provided by the project can be listed like so:
+
+    executables: bin/*
+
+One can also list the executables individually:
+
+    executables:
+     - util1
+     - util2
+
+If the `executables` are not listed, Ore will use the names of any
+executable file within the `bin/` directory.
+
+## default_executable
+
+The primary executable of the project can be listed like so:
+
+    default_executable: util1
+
+If `default_executable` is not listed, Ore will use the first element
+in `executables`.
+
+## has_rdoc
+
+One can specify the project contains [RDoc](http://rdoc.rubyforge.org/)
+documentation:
+
+    has_rdoc: true
+
+## has_yard
+
+If the project contains [YARD](http://yardoc.org/) and not
+[RDoc](http://rdoc.rubyforge.org/) documentation, one can specify this:
+
+    has_yard: true
+
+If neither `has_yard` or `has_rdoc` are listed, Ore will set `has_yard`
+if the `.yardopts` file exists in the root directory of the project.
+Otherwise, Ore will default `has_rdoc` to true.
+
+## extra_doc_files
+
+The extra files that should also be scanned for documentation can be listed
+like so:
+
+    extra_doc_files:
+     - ChangeLog.md
+     - LICENSE.txt
+
+If `extra_doc_files` is not listed, Ore will use the extra-files listed in
+the `.document` file.
+
+## files
+
+The files of the project can be listed like so:
+
+    file: lib/**/*.rb
+
+More than one file pattern can be specification:
+
+    file:
+     - lib/**/*.rb
+     - spec/**/*
+     - data/**/*
+
+If `files` is not listed, Ore will check if the project is using
+[Git](http://www.git-scm.org/), can will find all tracked files using:
+
+    git ls-files -z
+
+If the project is not using Git, Ore will default `files` to every file in
+the project.
+
+## test_files
+
+The files used to test the project can be listed like so:
+
+    test_files: spec/**/*_spec.rb
+
+More than one test-file pattern can be supplied:
+
+    test_files:
+     - spec/**/*_spec.rb
+     - features/**/*
+
+If `test_files` is not listed, Ore will default `files` to
+`test/{**/}test_*.rb` and `spec/{**/}*_spec.rb`.
+
+## required_ruby_version
+
+The version of Ruby required by the project can be listed like so:
+
+    required_ruby_version: >= 1.9.1
+
+## required_rubygems_version
+
+The version of RubyGems required by the project can be listed like so:
+
+    required_rubygems_version: >= 1.3.7
+
+If `required_rubygems_version` is not listed and the project uses Bundler,
+Ore will default `required_rubygems_version` to `>= 1.3.6`.
+
+## dependencies
+
+The dependencies of the project can be listed like so:
+
+    dependencies:
+      foo: ~> 0.1.0
+      bar: 1.2.3
+
+More than one version can be specified for each dependency:
+
+    dependencies:
+      foo: ~> 0.1.0, >= 0.0.7
+      bar: 1.2.3, 1.3.1
+
+## runtime_dependencies
+
+The purely runtime-dependencies for a project can be specified like so:
+
+    runtime_dependencies:
+      foo: ~> 0.1.0
+      bar: 1.2.3
+
+More than one version can be specified for each dependency:
+
+    dependencies:
+      foo: ~> 0.1.0, >= 0.0.7
+      bar: 1.2.3, 1.3.1
+
+## development_dependencies:
+
+The purely developmental-dependencies for a project can be specified
+like so:
+
+    development_dependencies:
+      foo: ~> 0.1.0
+      bar: 1.2.3
+
+More than one version can be specified for each dependency:
+
+    dependencies:
+      foo: ~> 0.1.0, >= 0.0.7
+      bar: 1.2.3, 1.3.1
+

data/LICENSE.txt

@@ -0,0 +1,21 @@
+
+Copyright (c) 2010 Hal Brodigan
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+'Software'), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,104 @@
+# Ore
+
+* [Source](http://github.com/postmodern/ore)
+* [Issues](http://github.com/postmodern/ore/issues)
+* IRC: irc.freenode.net #ruby-ore
+* Postmodern (postmodern.mod3 at gmail.com)
+
+## Description
+
+Ore is a simple RubyGem building solution. Ore handles the creation of
+`Gem::Specification` objects as well as building `.gem` files. Ore allows
+the developer to keep all of the project information in a single YAML file.
+
+## Features
+
+* Stores project information in **one YAML file** (`gemspec.yml`).
+* Has only **one** dependency ([thor](http://github.com/wycats/thor)).
+* **Does not** impose a development workflow onto the developer. One could
+  even use Ore with `Jeweler::Tasks`.
+* **Can** load the project version from:
+  * `VERSION` or `VERSION.yml` files.
+  * `VERSION` constants or `Version` modules defined in a `version.rb` file.
+* **Can** be used in traditional `.gemspec` files:
+
+      require 'ore/specification'
+      
+      Ore::Specification.new do |gemspec|
+        # custom logic here
+      end
+
+* Provides an **extendable** project **generator** that supports
+  user-installed templates.
+
+## Requirements
+
+* [thor](http://github.com/wycats/thor) ~> 0.14.3
+
+## Install
+
+    $ gem install ore
+
+## Example gemspec.yml files
+
+The `gemspec.yml` file used to build Ore:
+
+    name: ore
+    version: 0.1.2
+    summary: Cut raw RubyGems from YAML.
+    description:
+      Ore is a simple RubyGem building solution. Ore handles the
+      creation of Gem::Specification objects as well as building '.gem'
+      files. Ore allows the developer to keep all of the project information
+      in a single YAML file.
+    
+    license: MIT
+    authors: Postmodern
+    email: postmodern.mod3@gmail.com
+    homepage: http://github.com/postmodern/ore
+    has_yard: true
+    
+    dependencies:
+      thor: ~> 0.14.3
+    
+    development_dependencies:
+      yard: ~> 0.6.1
+      rspec: ~> 2.0.0
+
+For a complete refrence to the `gemspec.yml` file, please see
+{file:GemspecYML.md}.
+
+## Synopsis
+
+Install a custom template:
+
+    $ ore install http://github.com/user/awesometest.git
+
+List installed templates:
+
+    $ ore list
+
+Remove a previously installed template:
+
+    $ ore remove awesometest
+
+Generate a new project:
+
+    $ mine myproj
+
+Generate a new customized project:
+
+    $ mine myproj --bundler --rspec --yard
+
+Generate a new project using previously installed templates:
+
+    $ mine myproj --bundler --rspec --yard -T awesometest
+
+Builds a `.gem` file in the `pkg/` directory of a project:
+
+    $ ore
+
+## License
+
+See {file:LICENSE.txt} for license information.
+

data/Rakefile

@@ -0,0 +1,9 @@
+require 'rubygems'
+require 'rake'
+
+require 'rspec/core/rake_task'
+RSpec::Core::RakeTask.new
+task :default => :spec
+
+require 'yard'
+YARD::Rake::YardocTask.new

data/bin/mine

@@ -0,0 +1,12 @@
+#!/usr/bin/env ruby
+
+require 'rubygems'
+
+begin
+  require 'ore/generator'
+rescue LoadError => e
+  STDERR.puts 'Could not load "ore/generator"'
+  exit -1
+end
+
+Ore::Generator.start