gemrage 0.0.0

data/vendor/ruby/1.8/gems/jeweler-1.4.0/test/test_jeweler.rb

@@ -0,0 +1,187 @@
+require 'test_helper'
+
+class TestJeweler < Test::Unit::TestCase
+
+  def build_jeweler(base_dir = nil)
+    base_dir ||= git_dir_path
+    FileUtils.mkdir_p base_dir
+
+    Jeweler.new(build_spec, base_dir)
+  end
+
+  def git_dir_path
+    File.join(tmp_dir, 'git')
+  end
+
+  def non_git_dir_path
+    File.join(tmp_dir, 'nongit')
+  end
+
+  def build_git_dir
+
+    FileUtils.mkdir_p git_dir_path
+    Dir.chdir git_dir_path do
+      Git.init
+    end
+  end
+
+  def build_non_git_dir
+    FileUtils.mkdir_p non_git_dir_path
+  end
+
+  should "raise an error if a nil gemspec is given" do
+    assert_raises Jeweler::GemspecError do
+      Jeweler.new(nil)
+    end
+  end
+
+  should "know if it is in a git repo" do
+    build_git_dir
+
+    assert build_jeweler(git_dir_path).in_git_repo?
+  end
+
+  should "know if it is not in a git repo" do
+    build_non_git_dir
+
+    jeweler = build_jeweler(non_git_dir_path)
+    assert ! jeweler.in_git_repo?, "jeweler doesn't know that #{jeweler.base_dir} is not a git repository"
+  end
+
+  should "find the base repo" do
+    jeweler = build_jeweler(File.dirname(File.expand_path(__FILE__)))
+    assert_equal File.dirname(File.dirname(File.expand_path(__FILE__))), jeweler.git_base_dir
+  end
+
+  should "build and run write gemspec command when writing gemspec" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::WriteGemspec).build_for(jeweler) { command }
+
+    jeweler.write_gemspec
+  end
+
+  should "build and run validate gemspec command when validating gemspec" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::ValidateGemspec).build_for(jeweler) { command }
+
+    jeweler.validate_gemspec
+  end
+
+  should "build and run build gem command when building gem" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::BuildGem).build_for(jeweler) { command }
+
+    jeweler.build_gem
+  end
+
+  should "build and run build gem command when installing gem" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::InstallGem).build_for(jeweler) { command }
+
+    jeweler.install_gem
+  end
+
+  should "build and run bump major version command when bumping major version" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::Version::BumpMajor).build_for(jeweler) { command }
+
+    jeweler.bump_major_version
+  end
+
+  should "build and run bump minor version command when bumping minor version" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::Version::BumpMinor).build_for(jeweler) { command }
+
+    jeweler.bump_minor_version
+  end
+
+  should "build and run write version command when writing version" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+    mock(command).major=(1)
+    mock(command).minor=(5)
+    mock(command).patch=(2)
+    mock(command).build=('a1')
+
+    mock(Jeweler::Commands::Version::Write).build_for(jeweler) { command }
+
+    jeweler.write_version(1, 5, 2, 'a1')
+  end
+
+  should "build and run release to github command when running release_gem_to_github" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::ReleaseToGithub).build_for(jeweler) { command }
+
+    jeweler.release_gem_to_github
+  end
+
+  should "build and run release to git command when running release_to_git" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::ReleaseToGit).build_for(jeweler) { command }
+
+    jeweler.release_to_git
+  end
+
+  should "build and run release to rubyforge command when running release to rubyforge" do
+    jeweler = build_jeweler
+
+    command = Object.new
+    mock(command).run
+
+    mock(Jeweler::Commands::ReleaseToRubyforge).build_for(jeweler) { command }
+
+    jeweler.release_gem_to_rubyforge
+  end
+
+
+  should "respond to gemspec_helper" do
+    assert_respond_to build_jeweler, :gemspec_helper
+  end
+
+  should "respond to version_helper" do
+    assert_respond_to build_jeweler, :version_helper
+  end
+
+  should "respond to repo" do
+    assert_respond_to build_jeweler, :repo
+  end
+
+  should "respond to commit" do
+    assert_respond_to build_jeweler, :commit
+  end
+
+end

data/vendor/ruby/1.8/gems/json_pure-1.4.6/CHANGES

@@ -0,0 +1,179 @@
+2010-08-09 (1.4.6)
+  * Fixed oversight reported in http://github.com/flori/json/issues/closed#issue/23,
+    always create a new object from the state prototype.
+  * Made pure and ext api more similar again.
+2010-08-07 (1.4.5)
+  * Manage data structure nesting depth in state object during generation. This
+    should reduce problems with to_json method definіtions that only have one
+    argument.
+  * Some fixes in the state objects and additional tests.
+2010-08-06 (1.4.4)
+  * Fixes build problem for rubinius under OS X, http://github.com/flori/json/issues/closed#issue/25
+  * Fixes crashes described in http://github.com/flori/json/issues/closed#issue/21 and
+    http://github.com/flori/json/issues/closed#issue/23
+2010-05-05 (1.4.3)
+  * Fixed some test assertions, from Ruby r27587 and r27590, patch by nobu.
+  * Fixed issue http://github.com/flori/json/issues/#issue/20 reported by
+    electronicwhisper@github. Thx!
+2010-04-26 (1.4.2)
+  * Applied patch from naruse Yui NARUSE <naruse@airemix.com> to make building with
+    Microsoft Visual C possible again.
+  * Applied patch from devrandom <c1.github@niftybox.net> in order to allow building of
+    json_pure if extensiontask is not present.
+  * Thanks to Dustin Schneider <dustin@stocktwits.com>, who reported a memory
+    leak, which is fixed in this release.
+  * Applied 993f261ccb8f911d2ae57e9db48ec7acd0187283 patch from josh@github.
+2010-04-25 (1.4.1)
+  * Fix for a bug reported by Dan DeLeo <dan@kallistec.com>, caused by T_FIXNUM
+    being different on 32bit/64bit architectures.
+2010-04-23 (1.4.0)
+  * Major speed improvements and building with simplified
+    directory/file-structure.
+  * Extension should at least be comapatible with MRI, YARV and Rubinius.
+2010-04-07 (1.2.4)
+  * Triger const_missing callback to make Rails' dynamic class loading work.
+2010-03-11 (1.2.3)
+  * Added a State#[] method which returns an attribute's value in order to
+    increase duck type compatibility to Hash.
+2010-02-27 (1.2.2)
+  * Made some changes to make the building of the parser/generator compatible
+    to Rubinius.
+2009-11-25 (1.2.1)
+  * Added :symbolize_names option to Parser, which returns symbols instead of
+    strings in object names/keys.
+2009-10-01 (1.2.0)
+  * fast_generate now raises an exeception for nan and infinite floats.
+  * On Ruby 1.8 json supports parsing of UTF-8, UTF-16BE, UTF-16LE, UTF-32BE,
+    and UTF-32LE JSON documents now. Under Ruby 1.9 the M17n conversion
+    functions are used to convert from all supported encodings. ASCII-8BIT
+    encoded strings are handled like all strings under Ruby 1.8 were.
+  * Better documentation
+2009-08-23 (1.1.9)
+  * Added forgotten main doc file extra_rdoc_files.
+2009-08-23 (1.1.8)
+  * Applied a patch by OZAWA Sakuro <sakuro@2238club.org> to make json/pure
+    work in environments that don't provide iconv.
+  * Applied patch by okkez_ in order to fix Ruby Bug #1768:
+      http://redmine.ruby-lang.org/issues/show/1768.
+  * Finally got around to avoid the rather paranoid escaping of ?/ characters
+    in the generator's output. The parsers aren't affected by this change.
+    Thanks to Rich Apodaca <rapodaca@metamolecular.com> for the suggestion.
+2009-06-29 (1.1.7)
+  * Security Fix for JSON::Pure::Parser. A specially designed string could
+    cause catastrophic backtracking in one of the parser's regular expressions
+    in earlier 1.1.x versions. JSON::Ext::Parser isn't affected by this issue.
+    Thanks to Bartosz Blimke <bartosz@new-bamboo.co.uk> for reporting this
+    problem.
+  * This release also uses a less strict ruby version requirement for the
+    creation of the mswin32 native gem.
+2009-05-10 (1.1.6)
+  * No changes. І tested native linux gems in the last release and they don't
+    play well with different ruby versions other than the one the gem was built
+    with. This release is just to bump the version number in order to skip the
+    native gem on rubyforge.
+2009-05-10 (1.1.5)
+  * Started to build gems with rake-compiler gem.
+  * Applied patch object/array class patch from Brian Candler
+    <B.Candler@pobox.com> and fixes.
+2009-04-01 (1.1.4)
+  * Fixed a bug in the creation of serialized generic rails objects reported by
+    Friedrich Graeter <graeter@hydrixos.org>.
+  * Deleted tests/runner.rb, we're using testrb instead.
+  * Editor supports Infinity in numbers now.
+  * Made some changes in order to get the library to compile/run under Ruby
+    1.9.
+  * Improved speed of the code path for the fast_generate method in the pure
+    variant.
+2008-07-10 (1.1.3)
+  * Wesley Beary <monki@geemus.com> reported a bug in json/add/core's DateTime
+    handling: If the nominator and denominator of the offset were divisible by
+    each other Ruby's Rational#to_s returns them as an integer not a fraction
+    with '/'. This caused a ZeroDivisionError during parsing.
+  * Use Date#start and DateTime#start instead of sg method, while
+    remaining backwards compatible.
+  * Supports ragel >= 6.0 now.
+  * Corrected some tests.
+  * Some minor changes.
+2007-11-27 (1.1.2)
+  * Remember default dir (last used directory) in editor.
+  * JSON::Editor.edit method added, the editor can now receive json texts from
+    the clipboard via C-v.
+  * Load json texts from an URL pasted via middle button press.
+  * Added :create_additions option to Parser. This makes it possible to disable
+    the creation of additions by force, in order to treat json texts as data
+    while having additions loaded.
+  * Jacob Maine <jmaine@blurb.com> reported, that JSON(:foo) outputs a JSON
+    object if the rails addition is enabled, which is wrong. It now outputs a
+    JSON string "foo" instead, like suggested by Jacob Maine.
+  * Discovered a bug in the Ruby Bugs Tracker on rubyforge, that was reported
+    by John Evans lgastako@gmail.com. He could produce a crash in the JSON
+    generator by returning something other than a String instance from a
+    to_json method. I now guard against this by doing a rather crude type
+    check, which raises an exception instead of crashing.
+2007-07-06 (1.1.1)
+  * Yui NARUSE <naruse@airemix.com> sent some patches to fix tests for Ruby
+    1.9. I applied them and adapted some of them a bit to run both on 1.8 and
+    1.9.
+  * Introduced a JSON.parse! method without depth checking for people who like
+    danger.
+  * Made generate and pretty_generate methods configurable by an options hash.
+  * Added :allow_nan option to parser and generator in order to handle NaN,
+    Infinity, and -Infinity correctly - if requested. Floats, which aren't numbers,
+    aren't valid JSON according to RFC4627, so by default an exception will be
+    raised if any of these symbols are encountered. Thanks to Andrea Censi
+    <andrea.censi@dis.uniroma1.it> for his hint about this.
+  * Fixed some more tests for Ruby 1.9.
+  * Implemented dump/load interface of Marshal as suggested in ruby-core:11405
+    by murphy <murphy@rubychan.de>.
+  * Implemented the max_nesting feature for generate methods, too.
+  * Added some implementations for ruby core's custom objects for
+    serialisation/deserialisation purposes.
+2007-05-21 (1.1.0)
+  * Implemented max_nesting feature for parser to avoid stack overflows for
+    data from untrusted sources. If you trust the source, you can disable it
+    with the option max_nesting => false.
+  * Piers Cawley <pdcawley@bofh.org.uk> reported a bug, that not every
+    character can be escaped by ?\ as required by RFC4627. There's a
+    contradiction between David Crockford's JSON checker test vectors (in
+    tests/fixtures) and RFC4627, though. I decided to stick to the RFC, because
+    the JSON checker seems to be a bit older than the RFC.
+  * Extended license to Ruby License, which includes the GPL.
+  * Added keyboard shortcuts, and 'Open location' menu item to edit_json.rb.
+2007-05-09 (1.0.4)
+  * Applied a patch from Yui NARUSE <naruse@airemix.com> to make JSON compile
+    under Ruby 1.9. Thank you very much for mailing it to me!
+  * Made binary variants of JSON fail early, instead of falling back to the
+    pure version. This should avoid overshadowing of eventual problems while
+    loading of the binary.
+2007-03-24 (1.0.3)
+  * Improved performance of pure variant a bit.
+  * The ext variant of this release supports the mswin32 platform. Ugh!
+2007-03-24 (1.0.2)
+  * Ext Parser didn't parse 0e0 correctly into 0.0: Fixed!
+2007-03-24 (1.0.1)
+  * Forgot some object files in the build dir. I really like that - not!
+2007-03-24 (1.0.0)
+  * Added C implementations for the JSON generator and a ragel based JSON
+    parser in C.
+  * Much more tests, especially fixtures from json.org.
+  * Further improved conformance to RFC4627.
+2007-02-09 (0.4.3)
+  * Conform more to RFC4627 for JSON: This means JSON strings
+    now always must contain exactly one object "{ ... }" or array "[ ... ]" in
+    order to be parsed without raising an exception. The definition of what
+    constitutes a whitespace is narrower in JSON than in Ruby ([ \t\r\n]), and
+    there are differences in floats and integers (no octals or hexadecimals) as
+    well.
+  * Added aliases generate and pretty_generate of unparse and pretty_unparse.
+  * Fixed a test case.
+  * Catch an Iconv::InvalidEncoding exception, that seems to occur on some Sun
+    boxes with SunOS 5.8, if iconv doesn't support utf16 conversions. This was
+    reported by Andrew R Jackson <andrewj@bcm.tmc.edu>, thanks a bunch!
+2006-08-25 (0.4.2)
+  * Fixed a bug in handling solidi (/-characters), that was reported by
+    Kevin Gilpin <kevin.gilpin@alum.mit.edu>.
+2006-02-06 (0.4.1)
+  * Fixed a bug related to escaping with backslashes. Thanks for the report go
+    to Florian Munz <surf@theflow.de>.
+2005-09-23 (0.4.0)
+  * Initial Rubyforge Version

data/vendor/ruby/1.8/gems/json_pure-1.4.6/COPYING

@@ -0,0 +1,58 @@
+Ruby is copyrighted free software by Yukihiro Matsumoto <matz@netlab.co.jp>.
+You can redistribute it and/or modify it under either the terms of the GPL
+(see GPL file), or the conditions below:
+
+  1. You may make and give away verbatim copies of the source form of the
+     software without restriction, provided that you duplicate all of the
+     original copyright notices and associated disclaimers.
+
+  2. You may modify your copy of the software in any way, provided that
+     you do at least ONE of the following:
+
+       a) place your modifications in the Public Domain or otherwise
+          make them Freely Available, such as by posting said
+	  modifications to Usenet or an equivalent medium, or by allowing
+	  the author to include your modifications in the software.
+
+       b) use the modified software only within your corporation or
+          organization.
+
+       c) rename any non-standard executables so the names do not conflict
+	  with standard executables, which must also be provided.
+
+       d) make other distribution arrangements with the author.
+
+  3. You may distribute the software in object code or executable
+     form, provided that you do at least ONE of the following:
+
+       a) distribute the executables and library files of the software,
+	  together with instructions (in the manual page or equivalent)
+	  on where to get the original distribution.
+
+       b) accompany the distribution with the machine-readable source of
+	  the software.
+
+       c) give non-standard executables non-standard names, with
+          instructions on where to get the original software distribution.
+
+       d) make other distribution arrangements with the author.
+
+  4. You may modify and include the part of the software into any other
+     software (possibly commercial).  But some files in the distribution
+     are not written by the author, so that they are not under this terms.
+
+     They are gc.c(partly), utils.c(partly), regex.[ch], st.[ch] and some
+     files under the ./missing directory.  See each file for the copying
+     condition.
+
+  5. The scripts and library files supplied as input to or produced as 
+     output from the software do not automatically fall under the
+     copyright of the software, but belong to whomever generated them, 
+     and may be sold commercially, and may be aggregated with this
+     software.
+
+  6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
+     IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
+     WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+     PURPOSE.
+