development 1.1.0 → 1.1.1

data/README.md

@@ -4,13 +4,11 @@ http://rubygems.org/gems/development
 
 # Summary #
 
-Manage development contexts, particularly in the context of nested gem dependencies being developed side by side.
+Cause gem require to load a path other than the RubyGems installation.
 
 # 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.
+Intercept gem-require expression (require 'gem') and require version at alternative path (such as a development version).
 
 # Install #
 
@@ -37,22 +35,26 @@ end
 
 Doing this rather than simply requiring development ensures that Development can work transparently without requiring even a development dependency.
 
-## 2. Configure Gems Development Should Intercept ##
+## 2. Configure Which Gems Development Should Override ##
 
-The primary interface to development is the **.development** configuration file, which should be placed in the user's home directory.
+The primary interface to development is the **.development.rb** configuration file, which should be placed in the user's home directory.
 
-I would make project-specific .development files a requirement (to avoid accidentally enabling it) but I don't think there is a reliable way to find the project directory based on the require. If you know a way, please let me know!
+I would make project-specific .development.rb files a requirement (to avoid accidentally enabling it) but I don't think there is a reliable way to find the project directory based on the require. If you know a way, please let me know!
 
-### Configuration File Example ###
+### The .development.rb Configuration File ###
 
 #### Short Example ####
 
+The shortest possible example is a one-liner:
+
 ```ruby
 enable! :parallel_ancestry => '~/Projects/rp/ruby/parallel_ancestry'
 ```
 
 #### Extended Example ####
 
+But other configuration possibilities are provided for more complex configurations:
+
 ```ruby
 ###
 # Declare named locations to associate gems or gemsets with specific locations.
@@ -105,6 +107,29 @@ gem( 'to_lambda' ).directory( :ruby )
 enable! :ruby, :hooked_objects, :compositing_objects, :parallel_ancestry
 ```
 
+## Using Development with Bundler ##
+
+Development plays well with bundler. The only caveat is that you have to require Development before Bundler.require:
+
+```ruby
+require 'bundler'
+
+begin ; require 'development' ; rescue LoadError ; end
+
+Bundler.require
+```
+
+or
+
+```ruby
+begin ; require 'development' ; rescue LoadError ; end
+
+require 'bundler'
+
+Bundler.require
+```
+
+
 # License #
 
   (The MIT License)

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: development
 version: !ruby/object:Gem::Version
-  version: 1.1.0
+  version: 1.1.1
   prerelease: 
 platform: ruby
 authors:
@@ -9,18 +9,10 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-07-11 00:00:00.000000000 Z
+date: 2012-07-15 00:00:00.000000000 Z
 dependencies: []
-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.
+description: Intercept gem-require expression (require 'gem') and require version
+  at alternative path (such as a development version).
 email: asher@ridiculouspower.com
 executables: []
 extensions: []
@@ -72,7 +64,7 @@ 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.
+summary: Cause gem require (require 'gem') to load a path other than the RubyGems
+  installation.
 test_files: []
 has_rdoc: