development 1.0.0

data/spec/mock_gem-subgem/lib/mock_gem/subgem.rb

@@ -0,0 +1,4 @@
+
+class ::Development::MockGem::Subgem
+
+end

data/spec/mock_gem/lib/mock_gem.rb

@@ -0,0 +1,4 @@
+
+class ::Development::MockGem
+
+end

data/spec/other_require_mock/lib/other_require_mock.rb

@@ -0,0 +1,4 @@
+
+class ::Development::OtherRequireMock
+
+end

data/spec/require_mock/lib/require_mock.rb

@@ -0,0 +1,4 @@
+
+class ::Development::RequireMock
+
+end

metadata

@@ -0,0 +1,90 @@
+--- !ruby/object:Gem::Specification
+name: development
+version: !ruby/object:Gem::Version
+  version: 1.0.0
+  prerelease: 
+platform: ruby
+authors:
+- Asher
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2012-07-09 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: array-unique
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+description: Sometimes problems in one gem under development only appear in the context
+  of use in another gem. In these contexts it can be difficult to discern the particular
+  problem case without diving into the code. When gems are nested in multiple levels
+  of dependency, this can become quite frustrating; gem require paths have to be replaced
+  with relative paths, sometimes in multiple places, and it becomes easy to forget
+  that there are relative paths in code, resulting in production code with broken
+  development paths accidentally left in. Development inserts itself in the require
+  process and loads development paths instead of the gem requires used for production
+  code. Which gems load development paths instead of gem requires is determined by
+  a simple configuration file.
+email: asher@ridiculouspower.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- lib/development/exception/expression_error/unknown_directory_name.rb
+- lib/development/exception/expression_error/unknown_gem_or_gemset_name.rb
+- lib/development/exception/expression_error.rb
+- lib/development/exception/malformed_expression/malformed_enable_disable_expression.rb
+- lib/development/exception/malformed_expression/malformed_gemset_expression.rb
+- lib/development/exception/malformed_expression/malformed_general_directory_expression.rb
+- lib/development/exception/malformed_expression/malformed_location_expression.rb
+- lib/development/exception/malformed_expression/malformed_named_directory_expression.rb
+- lib/development/exception/malformed_expression/malformed_remove_general_directory_expression.rb
+- lib/development/exception/malformed_expression.rb
+- lib/development/require.rb
+- lib/development.rb
+- spec/development_spec.rb
+- spec/mock_gem/lib/mock_gem.rb
+- spec/mock_gem-subgem/lib/mock_gem/subgem.rb
+- spec/other_require_mock/lib/other_require_mock.rb
+- spec/require_mock/lib/require_mock.rb
+- README.md
+- CHANGELOG.md
+homepage: http://rubygems.org/gems/development
+licenses: []
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: development
+rubygems_version: 1.8.23
+signing_key: 
+specification_version: 3
+summary: Manage development contexts, particularly in the context of nested gem dependencies
+  being developed side by side.
+test_files: []
+has_rdoc: