license_finder 0.4.5 → 0.5.0

data/spec/fixtures/isc_licensed_gem/LICENSE

@@ -1,10 +0,0 @@
-Copyright (c) 2012, Pivotal Labs
-
-Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted,
-provided that the above copyright notice and this permission notice appear in all copies.
-
-THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
-IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
-INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
-ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF
-THIS SOFTWARE.

data/spec/fixtures/lgpl_licensed_gem/LICENSE

@@ -1,165 +0,0 @@
-                   GNU LESSER GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-
-  This version of the GNU Lesser General Public License incorporates
-the terms and conditions of version 3 of the GNU General Public
-License, supplemented by the additional permissions listed below.
-
-  0. Additional Definitions.
-
-  As used herein, "this License" refers to version 3 of the GNU Lesser
-General Public License, and the "GNU GPL" refers to version 3 of the GNU
-General Public License.
-
-  "The Library" refers to a covered work governed by this License,
-other than an Application or a Combined Work as defined below.
-
-  An "Application" is any work that makes use of an interface provided
-by the Library, but which is not otherwise based on the Library.
-Defining a subclass of a class defined by the Library is deemed a mode
-of using an interface provided by the Library.
-
-  A "Combined Work" is a work produced by combining or linking an
-Application with the Library.  The particular version of the Library
-with which the Combined Work was made is also called the "Linked
-Version".
-
-  The "Minimal Corresponding Source" for a Combined Work means the
-Corresponding Source for the Combined Work, excluding any source code
-for portions of the Combined Work that, considered in isolation, are
-based on the Application, and not on the Linked Version.
-
-  The "Corresponding Application Code" for a Combined Work means the
-object code and/or source code for the Application, including any data
-and utility programs needed for reproducing the Combined Work from the
-Application, but excluding the System Libraries of the Combined Work.
-
-  1. Exception to Section 3 of the GNU GPL.
-
-  You may convey a covered work under sections 3 and 4 of this License
-without being bound by section 3 of the GNU GPL.
-
-  2. Conveying Modified Versions.
-
-  If you modify a copy of the Library, and, in your modifications, a
-facility refers to a function or data to be supplied by an Application
-that uses the facility (other than as an argument passed when the
-facility is invoked), then you may convey a copy of the modified
-version:
-
-   a) under this License, provided that you make a good faith effort to
-   ensure that, in the event an Application does not supply the
-   function or data, the facility still operates, and performs
-   whatever part of its purpose remains meaningful, or
-
-   b) under the GNU GPL, with none of the additional permissions of
-   this License applicable to that copy.
-
-  3. Object Code Incorporating Material from Library Header Files.
-
-  The object code form of an Application may incorporate material from
-a header file that is part of the Library.  You may convey such object
-code under terms of your choice, provided that, if the incorporated
-material is not limited to numerical parameters, data structure
-layouts and accessors, or small macros, inline functions and templates
-(ten or fewer lines in length), you do both of the following:
-
-   a) Give prominent notice with each copy of the object code that the
-   Library is used in it and that the Library and its use are
-   covered by this License.
-
-   b) Accompany the object code with a copy of the GNU GPL and this license
-   document.
-
-  4. Combined Works.
-
-  You may convey a Combined Work under terms of your choice that,
-taken together, effectively do not restrict modification of the
-portions of the Library contained in the Combined Work and reverse
-engineering for debugging such modifications, if you also do each of
-the following:
-
-   a) Give prominent notice with each copy of the Combined Work that
-   the Library is used in it and that the Library and its use are
-   covered by this License.
-
-   b) Accompany the Combined Work with a copy of the GNU GPL and this license
-   document.
-
-   c) For a Combined Work that displays copyright notices during
-   execution, include the copyright notice for the Library among
-   these notices, as well as a reference directing the user to the
-   copies of the GNU GPL and this license document.
-
-   d) Do one of the following:
-
-       0) Convey the Minimal Corresponding Source under the terms of this
-       License, and the Corresponding Application Code in a form
-       suitable for, and under terms that permit, the user to
-       recombine or relink the Application with a modified version of
-       the Linked Version to produce a modified Combined Work, in the
-       manner specified by section 6 of the GNU GPL for conveying
-       Corresponding Source.
-
-       1) Use a suitable shared library mechanism for linking with the
-       Library.  A suitable mechanism is one that (a) uses at run time
-       a copy of the Library already present on the user's computer
-       system, and (b) will operate properly with a modified version
-       of the Library that is interface-compatible with the Linked
-       Version.
-
-   e) Provide Installation Information, but only if you would otherwise
-   be required to provide such information under section 6 of the
-   GNU GPL, and only to the extent that such information is
-   necessary to install and execute a modified version of the
-   Combined Work produced by recombining or relinking the
-   Application with a modified version of the Linked Version. (If
-   you use option 4d0, the Installation Information must accompany
-   the Minimal Corresponding Source and Corresponding Application
-   Code. If you use option 4d1, you must provide the Installation
-   Information in the manner specified by section 6 of the GNU GPL
-   for conveying Corresponding Source.)
-
-  5. Combined Libraries.
-
-  You may place library facilities that are a work based on the
-Library side by side in a single library together with other library
-facilities that are not Applications and are not covered by this
-License, and convey such a combined library under terms of your
-choice, if you do both of the following:
-
-   a) Accompany the combined library with a copy of the same work based
-   on the Library, uncombined with any other library facilities,
-   conveyed under the terms of this License.
-
-   b) Give prominent notice with the combined library that part of it
-   is a work based on the Library, and explaining where to find the
-   accompanying uncombined form of the same work.
-
-  6. Revised Versions of the GNU Lesser General Public License.
-
-  The Free Software Foundation may publish revised and/or new versions
-of the GNU Lesser General Public License from time to time. Such new
-versions will be similar in spirit to the present version, but may
-differ in detail to address new problems or concerns.
-
-  Each version is given a distinguishing version number. If the
-Library as you received it specifies that a certain numbered version
-of the GNU Lesser General Public License "or any later version"
-applies to it, you have the option of following the terms and
-conditions either of that published version or of any later version
-published by the Free Software Foundation. If the Library as you
-received it does not specify a version number of the GNU Lesser
-General Public License, you may choose any version of the GNU Lesser
-General Public License ever published by the Free Software Foundation.
-
-  If the Library as you received it specifies that a proxy can decide
-whether future versions of the GNU Lesser General Public License shall
-apply, that proxy's public statement of acceptance of any version is
-permanent authorization for you to choose that version for the
-Library.

data/spec/fixtures/mit_licensed_gem_in_README/README.rdoc

@@ -1,222 +0,0 @@
-= Active Record -- Object-relational mapping put on rails
-
-Active Record connects classes to relational database tables to establish an
-almost zero-configuration persistence layer for applications. The library
-provides a base class that, when subclassed, sets up a mapping between the new
-class and an existing table in the database. In context of an application,
-these classes are commonly referred to as *models*. Models can also be
-connected to other models; this is done by defining *associations*.
-
-Active Record relies heavily on naming in that it uses class and association
-names to establish mappings between respective database tables and foreign key
-columns. Although these mappings can be defined explicitly, it's recommended
-to follow naming conventions, especially when getting started with the
-library.
-
-A short rundown of some of the major features:
-
-* Automated mapping between classes and tables, attributes and columns.
-
-   class Product < ActiveRecord::Base
-   end
-
-   The Product class is automatically mapped to the table named "products",
-   which might look like this:
-
-   CREATE TABLE products (
-     id int(11) NOT NULL auto_increment,
-     name varchar(255),
-     PRIMARY KEY  (id)
-   );
-
-   This would also define the following accessors: `Product#name` and
-   `Product#name=(new_name)`
-
-  {Learn more}[link:classes/ActiveRecord/Base.html]
-
-
-* Associations between objects defined by simple class methods.
-
-   class Firm < ActiveRecord::Base
-     has_many   :clients
-     has_one    :account
-     belongs_to :conglomerate
-   end
-
-  {Learn more}[link:classes/ActiveRecord/Associations/ClassMethods.html]
-
-
-* Aggregations of value objects.
-
-   class Account < ActiveRecord::Base
-     composed_of :balance, :class_name => "Money",
-                 :mapping => %w(balance amount)
-     composed_of :address,
-                 :mapping => [%w(address_street street), %w(address_city city)]
-   end
-
-  {Learn more}[link:classes/ActiveRecord/Aggregations/ClassMethods.html]
-
-
-* Validation rules that can differ for new or existing objects.
-
-    class Account < ActiveRecord::Base
-      validates_presence_of     :subdomain, :name, :email_address, :password
-      validates_uniqueness_of   :subdomain
-      validates_acceptance_of   :terms_of_service, :on => :create
-      validates_confirmation_of :password, :email_address, :on => :create
-    end
-
-  {Learn more}[link:classes/ActiveRecord/Validations.html]
-
-
-* Callbacks available for the entire life cycle (instantiation, saving, destroying, validating, etc.)
-
-   class Person < ActiveRecord::Base
-     before_destroy :invalidate_payment_plan
-     # the `invalidate_payment_plan` method gets called just before Person#destroy
-   end
-
-  {Learn more}[link:classes/ActiveRecord/Callbacks.html]
-
-
-* Observers that react to changes in a model
-
-   class CommentObserver < ActiveRecord::Observer
-     def after_create(comment) # is called just after Comment#save
-       Notifications.deliver_new_comment("david@loudthinking.com", comment)
-     end
-   end
-
-  {Learn more}[link:classes/ActiveRecord/Observer.html]
-
-
-* Inheritance hierarchies
-
-   class Company < ActiveRecord::Base; end
-   class Firm < Company; end
-   class Client < Company; end
-   class PriorityClient < Client; end
-
-  {Learn more}[link:classes/ActiveRecord/Base.html]
-
-
-* Transactions
-
-    # Database transaction
-    Account.transaction do
-      david.withdrawal(100)
-      mary.deposit(100)
-    end
-
-  {Learn more}[link:classes/ActiveRecord/Transactions/ClassMethods.html]
-
-
-* Reflections on columns, associations, and aggregations
-
-    reflection = Firm.reflect_on_association(:clients)
-    reflection.klass # => Client (class)
-    Firm.columns # Returns an array of column descriptors for the firms table
-
-  {Learn more}[link:classes/ActiveRecord/Reflection/ClassMethods.html]
-
-
-* Database abstraction through simple adapters
-
-    # connect to SQLite3
-    ActiveRecord::Base.establish_connection(:adapter => "sqlite3", :database => "dbfile.sqlite3")
-
-    # connect to MySQL with authentication
-    ActiveRecord::Base.establish_connection(
-      :adapter  => "mysql",
-      :host     => "localhost",
-      :username => "me",
-      :password => "secret",
-      :database => "activerecord"
-    )
-
-  {Learn more}[link:classes/ActiveRecord/Base.html] and read about the built-in support for
-  MySQL[link:classes/ActiveRecord/ConnectionAdapters/MysqlAdapter.html],
-  PostgreSQL[link:classes/ActiveRecord/ConnectionAdapters/PostgreSQLAdapter.html], and
-  SQLite3[link:classes/ActiveRecord/ConnectionAdapters/SQLite3Adapter.html].
-
-
-* Logging support for Log4r[http://log4r.sourceforge.net] and Logger[http://www.ruby-doc.org/stdlib/libdoc/logger/rdoc]
-
-    ActiveRecord::Base.logger = Logger.new(STDOUT)
-    ActiveRecord::Base.logger = Log4r::Logger.new("Application Log")
-
-
-* Database agnostic schema management with Migrations
-
-    class AddSystemSettings < ActiveRecord::Migration
-      def self.up
-        create_table :system_settings do |t|
-          t.string  :name
-          t.string  :label
-          t.text    :value
-          t.string  :type
-          t.integer :position
-        end
-
-        SystemSetting.create :name => "notice", :label => "Use notice?", :value => 1
-      end
-
-      def self.down
-        drop_table :system_settings
-      end
-    end
-
-  {Learn more}[link:classes/ActiveRecord/Migration.html]
-
-
-== Philosophy
-
-Active Record is an implementation of the object-relational mapping (ORM)
-pattern[http://www.martinfowler.com/eaaCatalog/activeRecord.html] by the same
-name described by Martin Fowler:
-
-  "An object that wraps a row in a database table or view,
-  encapsulates the database access, and adds domain logic on that data."
-
-Active Record attempts to provide a coherent wrapper as a solution for the inconvenience that is
-object-relational mapping. The prime directive for this mapping has been to minimize
-the amount of code needed to build a real-world domain model. This is made possible
-by relying on a number of conventions that make it easy for Active Record to infer
-complex relations and structures from a minimal amount of explicit direction.
-
-Convention over Configuration:
-* No XML-files!
-* Lots of reflection and run-time extension
-* Magic is not inherently a bad word
-
-Admit the Database:
-* Lets you drop down to SQL for odd cases and performance
-* Doesn't attempt to duplicate or replace data definitions
-
-
-== Download and installation
-
-The latest version of Active Record can be installed with Rubygems:
-
-  % [sudo] gem install activerecord
-
-Source code can be downloaded as part of the Rails project on GitHub
-
-* http://github.com/rails/rails/tree/master/activerecord/
-
-
-== License
-
-Active Record is released under the MIT license.
-
-
-== Support
-
-API documentation is at
-
-* http://api.rubyonrails.com
-
-Bug reports and feature requests can be filed with the rest for the Ruby on Rails project here:
-
-* https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets

data/spec/fixtures/mit_licensed_gem_via_url/README

@@ -1,210 +0,0 @@
-= Project: Builder
-
-== Goal
-
-Provide a simple way to create XML markup and data structures.
-
-== Classes
-
-Builder::XmlMarkup:: Generate XML markup notiation
-Builder::XmlEvents:: Generate XML events (i.e. SAX-like)
-
-<b>Notes</b>:: 
-
-* An <tt>Builder::XmlTree</tt> class to generate XML tree
-  (i.e. DOM-like) structures is also planned, but not yet implemented.
-  Also, the events builder is currently lagging the markup builder in
-  features.
-
-== Usage
-
-  require 'rubygems'	
-  require_gem 'builder', '~> 2.0'
-
-  builder = Builder::XmlMarkup.new
-  xml = builder.person { |b| b.name("Jim"); b.phone("555-1234") }
-  xml #=> <person><name>Jim</name><phone>555-1234</phone></person>
-
-or
-
-  require 'rubygems'	
-  require_gem 'builder'
-
-  builder = Builder::XmlMarkup.new(:target=>STDOUT, :indent=>2)
-  builder.person { |b| b.name("Jim"); b.phone("555-1234") }
-  #
-  # Prints:
-  # <person>
-  #   <name>Jim</name>
-  #   <phone>555-1234</phone>
-  # </person>
-
-== Compatibility
-
-=== Version 2.0.0 Compatibility Changes
-
-Version 2.0.0 introduces automatically escaped attribute values for
-the first time.  Versions prior to 2.0.0 did not insert escape
-characters into attribute values in the XML markup.  This allowed
-attribute values to explicitly reference entities, which was
-occasionally used by a small number of developers.  Since strings
-could always be explicitly escaped by hand, this was not a major
-restriction in functionality.
-
-However, it did suprise most users of builder.  Since the body text is
-normally escaped, everybody expected the attribute values to be
-escaped as well.  Escaped attribute values were the number one support
-request on the 1.x Builder series.
-
-Starting with Builder version 2.0.0, all attribute values expressed as
-strings will be processed and the appropriate characters will be
-escaped (e.g. "&" will be tranlated to "&amp;").  Attribute values
-that are expressed as Symbol values will not be processed for escaped
-characters and will be unchanged in output. (Yes, this probably counts
-as Symbol abuse, but the convention is convenient and flexible).
-
-Example:
-
-  xml = Builder::XmlMarkup.new
-  xml.sample(:escaped=>"This&That", :unescaped=>:"Here&amp;There")
-  xml.target!  =>
-    <sample escaped="This&amp;That" unescaped="Here&amp;There"/>
-
-=== Version 1.0.0 Compatibility Changes
-
-Version 1.0.0 introduces some changes that are not backwards
-compatible with earlier releases of builder.  The main areas of
-incompatibility are:
-
-* Keyword based arguments to +new+ (rather than positional based).  It
-  was found that a developer would often like to specify indentation
-  without providing an explicit target, or specify a target without
-  indentation.  Keyword based arguments handle this situation nicely.
-
-* Builder must now be an explicit target for markup tags.  Instead of
-  writing
-
-    xml_markup = Builder::XmlMarkup.new
-    xml_markup.div { strong("text") }
-
-  you need to write
-
-    xml_markup = Builder::XmlMarkup.new
-    xml_markup.div { xml_markup.strong("text") }
-
-* The builder object is passed as a parameter to all nested markup
-  blocks.  This allows you to create a short alias for the builder
-  object that can be used within the block.  For example, the previous
-  example can be written as:
-
-    xml_markup = Builder::XmlMarkup.new
-    xml_markup.div { |xml| xml.strong("text") }
-
-* If you have both a pre-1.0 and a post-1.0 gem of builder installed,
-  you can choose which version to use through the RubyGems
-  +require_gem+ facility.
-
-    require_gem 'builder', "~> 0.0"   # Gets the old version
-    require_gem 'builder', "~> 1.0"   # Gets the new version
-
-== Features
-
-* XML Comments are supported ...
-
-    xml_markup.comment! "This is a comment"
-      #=>  <!-- This is a comment -->
-
-* XML processing instructions are supported ...
-
-    xml_markup.instruct! :xml, :version=>"1.0", :encoding=>"UTF-8"
-      #=>  <?xml version="1.0" encoding="UTF-8"?>
-   
-  If the processing instruction is omitted, it defaults to "xml".
-  When the processing instruction is "xml", the defaults attributes
-  are:
-  
-  <b>version</b>:: 1.0
-  <b>encoding</b>:: "UTF-8"
-
-* XML entity declarations are now supported to a small degree.
-
-    xml_markup.declare! :DOCTYPE, :chapter, :SYSTEM, "../dtds/chapter.dtd"
-      #=>  <!DOCTYPE chapter SYSTEM "../dtds/chapter.dtd">
-
-  The parameters to a declare! method must be either symbols or
-  strings. Symbols are inserted without quotes, and strings are
-  inserted with double quotes.  Attribute-like arguments in hashes are
-  not allowed.
-
-  If you need to have an argument to declare! be inserted without
-  quotes, but the arguement does not conform to the typical Ruby
-  syntax for symbols, then use the :"string" form to specify a symbol.
-
-  For example:
-
-    xml_markup.declare! :ELEMENT, :chapter, :"(title,para+)"
-      #=>  <!ELEMENT chapter (title,para+)>
-
-  Nested entity declarations are allowed.  For example:
-
-    @xml_markup.declare! :DOCTYPE, :chapter do |x|
-      x.declare! :ELEMENT, :chapter, :"(title,para+)"
-      x.declare! :ELEMENT, :title, :"(#PCDATA)"
-      x.declare! :ELEMENT, :para, :"(#PCDATA)"
-    end
-
-    #=>
-
-    <!DOCTYPE chapter [
-      <!ELEMENT chapter (title,para+)>
-      <!ELEMENT title (#PCDATA)>
-      <!ELEMENT para (#PCDATA)>
-    ]>
-
-* Some support for XML namespaces is now available.  If the first
-  argument to a tag call is a symbol, it will be joined to the tag to
-  produce a namespace:tag combination.  It is easier to show this than
-  describe it.
-
-   xml.SOAP :Envelope do ... end
-
-  Just put a space before the colon in a namespace to produce the
-  right form for builder (e.g. "<tt>SOAP:Envelope</tt>" =>
-  "<tt>xml.SOAP :Envelope</tt>")
-
-* String attribute values are <em>now</em> escaped by default by
-  Builder (<b>NOTE:</b> this is _new_ behavior as of version 2.0).
-
-  However, occasionally you need to use entities in attribute values.
-  Using a symbols (rather than a string) for an attribute value will
-  cause Builder to not run its quoting/escaping algorithm on that
-  particular value.
-
-  (<b>Note:</b> The +escape_attrs+ option for builder is now
-  obsolete).
-
-  Example:
-
-    xml = Builder::XmlMarkup.new
-    xml.sample(:escaped=>"This&That", :unescaped=>:"Here&amp;There")
-    xml.target!  =>
-      <sample escaped="This&amp;That" unescaped="Here&amp;There"/>
-
-* UTF-8 Support
-
-  Builder correctly translates UTF-8 characters into valid XML.  (New
-  in version 2.0.0).  Thanks to Sam Ruby for the translation code.
-
-  Example:
-
-    xml = Builder::Markup.new
-    xml.sample("I?t?rn?ti?n?l")
-    xml.target!  =>
-      "<sample>I&#241;t&#235;rn&#226;ti&#244;n&#224;l</sample>"
-
-== Contact
-
-Author::     Jim Weirich
-Email::      jim@weirichhouse.org
-Home Page::  http://onestepback.org
-License::    MIT Licence (http://www.opensource.org/licenses/mit-license.html)