svn commit: r647051 - /incubator/buildr/trunk/doc/pages/more_stuff.textile

[as...@apache.org]

Author: assaf
Date: Thu Apr 10 22:39:28 2008
New Revision: 647051

URL: http://svn.apache.org/viewvc?rev=647051&view=rev
Log:
Removed section about addon, which is no longer relevant.

Modified:
    incubator/buildr/trunk/doc/pages/more_stuff.textile

Modified: incubator/buildr/trunk/doc/pages/more_stuff.textile
URL: http://svn.apache.org/viewvc/incubator/buildr/trunk/doc/pages/more_stuff.textile?rev=647051&r1=647050&r2=647051&view=diff
==============================================================================
--- incubator/buildr/trunk/doc/pages/more_stuff.textile (original)
+++ incubator/buildr/trunk/doc/pages/more_stuff.textile Thu Apr 10 22:39:28 2008
@@ -1,82 +1,6 @@
 h1. More Stuff
 
 
-h2.  Addons
-
-Addons allow you to package and distribute common extensions, tasks and
-features for use with different buildfiles.
-
-Addons are based on "RubyGems":http://www.rubygems.org/, a packaging and
-distribution mechanism for Ruby libraries.  Buildr itself is packaged as a Ruby
-gem, as are most of its dependencies.  Managing gems is done through the @gem@
-command line tool.
-
-The @require@ method allows you to include any Ruby file contained in a
-previously installed gem.  If multiple versions are installed, it will default to
-the most recent version.  You can change it to use a particular version with the
-@gem@ method, for example:
-
-{{{!ruby
-gem 'highline', '~> 1.4'
-require 'highline'
-}}}
-
-The @addon@ method replaces the @gem@ method and adds a couple of conveniences
-specifically for use in buildfiles.  Like the @gem@ method, it will activate
-the most recent version allowed.  However, if the gem does not already exists
-in the local repository, it will attempt to download and install it from one of
-the remote gem repositories.
-
-In addition, it will activate the gem.  
-
-
-The @addon@ method provides a convenient way to download and install a
-particular gem and make it available in your buildfile.  The method takes two
-arguments, the gem name and an optional version requirement.  For example:
-
-{{{!
-#  Latest version of extra and version 2.2 of shared.
-addon 'extra'
-addon 'shared', '2.2'
-}}}
-
-The version requirement can be an exact version number, or combine a comparison
-operator with a version number.  
-
-Supported comparison operators are @=@, @!=@, @>@, @<@, @>=@, @<=@ and @~>@.
-The compatible comparison (@~>@) matches from the specified version up one version.
-For example, @~> 5.3.1@ will match all versions from 5.3.1 up to but excluding 5.4,
-while @~> 5.3@ will match all versions from 5.3.0 up to but excluding 6.
-
-If multiple versions match, the highest is always picked.  The default version
-requirement, if unspecified, is @'>= 0@.  You can always use an array for more
-precise control, for example, to support all versions from 1.0 through 1.7,
-exclusing 1.3: @['>= 1.0', '<= 1.7', '!= 1.3']@.
-
-When running the build, the @addon@ methods attempts to find and activate the
-named gem from the local Gem repository.  If it can't find the gem or a matching
-version, it will attempt to download it from one of the remote gem repositories.
-
-What happens next depends on the specific addon.  The @addon@ method will load
-Ruby files places in the gem's require paths.  Some addons will use that to
-define methods, extend @Project@, define tasks, etc.  It will also import all
-@.rake@ files found in the gem's @tasks@ directory, which can be used to
-provide additional tasks.  Last, some addons will do nothing, but will make
-features available for inclusion, typically using a subsequent @require@.
-Consult the addon's documentation for more details.
-
-RubyGems uses the "RubyForge gems repository":http://gems.rubyforge.org/ as the
-default remote repository.  You can add additional sources using the @gem
-sources@ command, for example:
-
-{{{!sh
-$ # View all sources
-$ gem sources --list
-$ # Add another repository
-$ gem sources --add http://gems.example.com
-}}}
-
-
 h2.  Using Java Libraries
 
 Buildr runs along side a JVM, using either RJB or JRuby.  The Java module