Author: assaf
Date: Tue Jul 29 12:44:47 2008
New Revision: 680813

URL: http://svn.apache.org/viewvc?rev=680813&view=rev
Log:
Docs: BUILDR-111 Troubleshoot tip when Buildr's bin directory shows up in 
RUBYLIB (Geoffrey Ruscoe).

Modified:
    incubator/buildr/trunk/CHANGELOG
    incubator/buildr/trunk/doc/pages/troubleshooting.textile

Modified: incubator/buildr/trunk/CHANGELOG
URL: 
http://svn.apache.org/viewvc/incubator/buildr/trunk/CHANGELOG?rev=680813&r1=680812&r2=680813&view=diff
==============================================================================
--- incubator/buildr/trunk/CHANGELOG (original)
+++ incubator/buildr/trunk/CHANGELOG Tue Jul 29 12:44:47 2008
@@ -14,6 +14,8 @@
 * Fixed: BUILDR-110 Error creating buildfile from POM when missing plugin
 configuration (Geoffrey Ruscoe).
 * Fixed: BUILDR-112 Using a user gem repository with 'rake setup' (Lacton).
+* Docs: BUILDR-111 Troubleshoot tip when Buildr's bin directory shows up in
+RUBYLIB (Geoffrey Ruscoe).
 
 1.3.2 (2008-07-18)
 * Added: --prereqs command line argument to show all tasks and their

Modified: incubator/buildr/trunk/doc/pages/troubleshooting.textile
URL: 
http://svn.apache.org/viewvc/incubator/buildr/trunk/doc/pages/troubleshooting.textile?rev=680813&r1=680812&r2=680813&view=diff
==============================================================================
--- incubator/buildr/trunk/doc/pages/troubleshooting.textile (original)
+++ incubator/buildr/trunk/doc/pages/troubleshooting.textile Tue Jul 29 
12:44:47 2008
@@ -119,3 +119,28 @@
 end
 }}}
 
+
+h2. Buildr fails to run after install with a "stack level too deep
+(SystemStackError)" error
+
+A particular quirk of an existing Ruby setup can cause problems when running
+Buildr.  If a system already has several Ruby directories that are in the
[EMAIL PROTECTED]@, it is often nice (appropriate?) to have them in @RUBYLIB@ 
as well (to
+be able to require them).  If there are several of them a user may decide that
[EMAIL PROTECTED]@ is a good way to handle this (or some less automated method
+that has the same effect).
+
+The culprit is having the Gem's binary directory show up in @[EMAIL PROTECTED] 
 For
+example, Buildr's @bin/buildr@ includes this line:
+
+{{{!sh
+require 'buildr'
+}}}
+
+Under normal circumstances, this tells RubyGems to load @buildr.rb@ from
+the Gem's library directory.  When @RUBYLIB@ points to the Gem's @bin@
+directory, it ends up loading itself repeatedly. 
+
+To solve this, remove Buildr's @bin@ directory from @[EMAIL PROTECTED]  
Removing all
+directories that you don't actually need is better (other Gems may have the
+same problem).
\ No newline at end of file


Reply via email to