vclog 1.9.1 → 1.9.2

data/COPYING.rdoc

@@ -1,32 +0,0 @@
-= COPYRIGHT NOTICES
-
-== VCLog
-
-Copyright:: (c) 2008 Rubyworks
-License:: BSD-2-Clause
-Website:: http://rubyworks.github.com/vclog
-
-  Copyright 2008 Rubyworks. All rights reserved.
-
-  Redistribution and use in source and binary forms, with or without
-  modification, are permitted provided that the following conditions are met:
-
-     1. Redistributions of source code must retain the above copyright notice,
-        this list of conditions and the following disclaimer.
-
-     2. Redistributions in binary form must reproduce the above copyright
-        notice, this list of conditions and the following disclaimer in the
-        documentation and/or other materials provided with the distribution.
-
-  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
-  INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
-  AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-  COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-  INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-  NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR  SERVICES; LOSS OF USE,
-  DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
-  OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-  NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
-  EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-

data/features/git.feature

@@ -1,86 +0,0 @@
-Feature: Git Support
-  As a Git user
-  I want to generate a nicely formatted Changelog
-  And I want to generate a nicely formatted Release History
-
-  Scenario: Git Changelog
-    Given a suitable Git repository
-    When I run `vclog`
-    Then the exit status should be 0
-
-  Scenario: Git Changelog in RDoc
-    Given a suitable Git repository
-    When I run `vclog -f rdoc`
-    Then the exit status should be 0
-
-  Scenario: Git Changelog in Markdown
-    Given a suitable Git repository
-    When I run `vclog -f markdown`
-    Then the exit status should be 0
-
-  Scenario: Git Changelog in HTML
-    Given a suitable Git repository
-    When I run `vclog -f html`
-    Then the exit status should be 0
-
-  Scenario: Git Changelog in XML
-    Given a suitable Git repository
-    When I run `vclog -f xml`
-    Then the exit status should be 0
-
-  Scenario: Git Changelog in Atom
-    Given a suitable Git repository
-    When I run `vclog -f atom`
-    Then the exit status should be 0
-
-  Scenario: Git Changelog in YAML
-    Given a suitable Git repository
-    When I run `vclog -f yaml`
-    Then the exit status should be 0
-
-  Scenario: Git Changelog in JSON
-    Given a suitable Git repository
-    When I run `vclog -f json`
-    Then the exit status should be 0
-
-
-  Scenario: Git Release History
-    Given a suitable Git repository
-    When I run `vclog r`
-    Then the exit status should be 0
-
-  Scenario: Git Release History in RDoc
-    Given a suitable Git repository
-    When I run `vclog r -f rdoc`
-    Then the exit status should be 0
-
-  Scenario: Git Release History in Markdown
-    Given a suitable Git repository
-    When I run `vclog rel -f markdown`
-    Then the exit status should be 0
-
-  Scenario: Git Release History in HTML
-    Given a suitable Git repository
-    When I run `vclog rel -f html`
-    Then the exit status should be 0
-
-  Scenario: Git Release History in XML
-    Given a suitable Git repository
-    When I run `vclog rel -f xml`
-    Then the exit status should be 0
-
-  Scenario: Git Release History in Atom
-    Given a suitable Git repository
-    When I run `vclog rel -f atom`
-    Then the exit status should be 0
-
-  Scenario: Git Release History in YAML
-    Given a suitable Git repository
-    When I run `vclog rel -f yaml`
-    Then the exit status should be 0
-
-  Scenario: Git Release History in JSON
-    Given a suitable Git repository
-    When I run `vclog rel -f json`
-    Then the exit status should be 0
-

data/features/hg.feature

@@ -1,86 +0,0 @@
-Feature: Mercurial Support
-  As a Mercurial user
-  I want to generate a nicely formatted Changelog
-  And I want to generate a nicely formatted Release History
-
-  Scenario: Mercurial Changelog
-    Given a suitable Mercurial repository
-    When I run `vclog`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Changelog in RDoc
-    Given a suitable Mercurial repository
-    When I run `vclog -f rdoc`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Changelog in Markdown
-    Given a suitable Mercurial repository
-    When I run `vclog -f markdown`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Changelog in HTML
-    Given a suitable Mercurial repository
-    When I run `vclog -f html`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Changelog in XML
-    Given a suitable Mercurial repository
-    When I run `vclog -f xml`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Changelog in Atom
-    Given a suitable Mercurial repository
-    When I run `vclog -f atom`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Changelog in YAML
-    Given a suitable Mercurial repository
-    When I run `vclog -f yaml`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Changelog in JSON
-    Given a suitable Mercurial repository
-    When I run `vclog -f json`
-    Then the exit status should be 0
-
-
-  Scenario: Mercurial Release History
-    Given a suitable Mercurial repository
-    When I run `vclog rel`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Release History in RDoc
-    Given a suitable Mercurial repository
-    When I run `vclog rel -f rdoc`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Release History in Markdown
-    Given a suitable Mercurial repository
-    When I run `vclog rel -f markdown`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Release History in HTML
-    Given a suitable Mercurial repository
-    When I run `vclog rel -f html`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Release History in XML
-    Given a suitable Mercurial repository
-    When I run `vclog rel -f xml`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Release History in Atom
-    Given a suitable Mercurial repository
-    When I run `vclog rel -f atom`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Release History in YAML
-    Given a suitable Mercurial repository
-    When I run `vclog rel -f yaml`
-    Then the exit status should be 0
-
-  Scenario: Mercurial Release History in JSON
-    Given a suitable Mercurial repository
-    When I run `vclog rel -f json`
-    Then the exit status should be 0
-

data/features/step_definitions/history_steps.rb

@@ -1,29 +0,0 @@
-Given /^a SVN repository/ do
-  @directory = File.dirname(__FILE__) + '/../../test/fixtures/tzinfo'
-  @tag_numbers = Dir["@directory/tags/*"].map{ |d| File.basename(d) }
-end
-
-# For git we will have to use the VCLog project itself, I guess.
-Given /^a Git repository/ do
-  @directory = File.dirname(__FILE__) + '/../..' #/fixtures/git-repo'
-  tags1 = `cd #{@directory}; git tag -l "[0-9]*"`
-  tags2 = `cd #{@directory}; git tag -l "v[0-9]*"`
-  @tag_numbers = tags1.split("\n") + tags2.split("\n")
-end
-
-When /I generate a History/ do
-  @system  = VCLog::VCS.factory(@directory)
-  @history = VCLog::History.new(@system)
-end
-
-Then /it should include all tags/ do
-  tags = @history.tags.map{ |t| t.name }
-  tags.sort.assert == @tag_numbers.sort
-end
-
-And /^the list of releases should be in order from newest to oldest/ do
-  rels_names = @history.releases.map{ |r| r.tag.name }
-  rels_names.shift # remove imaginary current tag
-  rels_names.assert == @tag_numbers.sort.reverse
-end
-

data/features/step_definitions/repo_steps.rb

@@ -1,72 +0,0 @@
-Given /a suitable Subversion repository/ do
-  url    = "svn://rubyforge.org/var/svn/rubygems"
-  name   = "rubygems"
-  type   = "svn"
-  marker = ".svn"
-  clone  = "svn checkout #{url} #{name}"
-
-  setup_repo(name, type, marker, clone)
-
-  #dir = File.expand_path("tmp/hold/#{type}")
-  #unless File.exist?("#{dir}/#{name}/.svn")
-  #  `mkdir -p #{dir}; cd #{dir}; svn checkout #{url} #{name}`
-  #end
-  #create_dir(type)
-  #cd(type)
-  #run "cp -r #{dir} #{name}"
-  #cd(name)
-end
-
-Given /a suitable Git repository/ do
-  url    = "git://github.com/rubyworks/vclog.git"
-  name   = "vclog"
-  type   = "git"
-  marker = ".git"
-  clone  = "git clone #{url} #{name}"
-
-  setup_repo(name, type, marker, clone)
-
-  #create_dir('git')
-  #cd('git')
-  #unless File.exist?("#{name}/.git")
-  #  cmd = "git clone #{url} #{name}"
-  #  run cmd
-  #end
-  #cd(name)
-end
-
-Given /a suitable Mercurial repository/ do
-  url    = "http://bitbucket.org/birkenfeld/sphinx"
-  name   = "sphinx"
-  type   = "hg"
-  marker = ".hg"
-  clone  = "hg clone #{url} #{name}"
-
-  setup_repo(name, type, marker, clone)
-
-  #create_dir('hg')
-  #cd('hg')
-  #unless File.exist?("#{name}/.hg")
-  #  cmd = "hg clone #{url} #{name}"
-  #  run cmd
-  #end
-  #cd(name)
-end
-
-# TODO
-Given /a suitable Darcs repository/ do
-  url  = 
-  name = 
-  type   = "darcs"
-  marker = "_darcs"
-  clone  = ""
-
-  #create_dir('darcs')
-  #cd('darcs')
-  #unless File.exist?("#{name}/_darcs")
-  #  cmd = "darcs clone "
-  #  #run cmd
-  #end
-  #cd(name)
-end
-

data/features/support/ae.rb

@@ -1 +0,0 @@
-require 'ae'

data/features/support/aruba.rb

@@ -1,5 +0,0 @@
-require 'aruba/cucumber'
-
-Before do
-  @aruba_timeout_seconds = 20
-end

data/features/support/loadpath.rb

@@ -1,2 +0,0 @@
-$LOAD_PATH.unshift( File.dirname(__FILE__) + '/../../lib' )
-require 'vclog'

data/features/support/repo.rb

@@ -1,19 +0,0 @@
-#
-def setup_repo(name, type, marker, clone_command)
-  dir = File.expand_path("tmp/hold/#{type}")
-  dst = File.expand_path("tmp/aruba")
-
-  unless File.exist?("#{dir}/#{name}/#{marker}")
-    $stderr.puts("    #{clone_command}")
-    `mkdir -p #{dir}` unless File.directory?(dir)
-    `cd #{dir}; #{clone_command}`
-  end
-
-  #unless File.exist?("tmp/aruba/#{type}/#{name}")
-    `mkdir -p #{dst}`
-    `cp -r #{dir} #{dst}/#{type}/`
-  #end
-
-  cd("#{type}/#{name}")
-end
-

data/features/svn.feature

@@ -1,86 +0,0 @@
-Feature: Subversion Support
-  As a Subversion user
-  I want to generate a nicely formatted Changelog
-  And I want to generate a nicely formatted Release History
-
-  Scenario: Subversion Changelog
-    Given a suitable Subversion repository
-    When I run `vclog`
-    Then the exit status should be 0
-
-  Scenario: Subversion Changelog in RDoc
-    Given a suitable Subversion repository
-    When I run `vclog -f rdoc`
-    Then the exit status should be 0
-
-  Scenario: Subversion Changelog in Markdown
-    Given a suitable Subversion repository
-    When I run `vclog -f markdown`
-    Then the exit status should be 0
-
-  Scenario: Subversion Changelog in HTML
-    Given a suitable Subversion repository
-    When I run `vclog -f html`
-    Then the exit status should be 0
-
-  Scenario: Subversion Changelog in XML
-    Given a suitable Subversion repository
-    When I run `vclog -f xml`
-    Then the exit status should be 0
-
-  Scenario: Subversion Changelog in Atom
-    Given a suitable Subversion repository
-    When I run `vclog -f atom`
-    Then the exit status should be 0
-
-  Scenario: Subversion Changelog in YAML
-    Given a suitable Subversion repository
-    When I run `vclog -f yaml`
-    Then the exit status should be 0
-
-  Scenario: Subversion Changelog in JSON
-    Given a suitable Subversion repository
-    When I run `vclog -f json`
-    Then the exit status should be 0
-
-
-  Scenario: Subversion Release History
-    Given a suitable Subversion repository
-    When I run `vclog rel`
-    Then the exit status should be 0
-
-  Scenario: Subversion Release History in RDoc
-    Given a suitable Subversion repository
-    When I run `vclog rel -f rdoc`
-    Then the exit status should be 0
-
-  Scenario: Subversion Release History in Markdown
-    Given a suitable Subversion repository
-    When I run `vclog rel -f markdown`
-    Then the exit status should be 0
-
-  Scenario: Subversion Release History in HTML
-    Given a suitable Subversion repository
-    When I run `vclog rel -f html`
-    Then the exit status should be 0
-
-  Scenario: Subversion Release History in XML
-    Given a suitable Subversion repository
-    When I run `vclog rel -f xml`
-    Then the exit status should be 0
-
-  Scenario: Subversion Release History in Atom
-    Given a suitable Subversion repository
-    When I run `vclog rel -f atom`
-    Then the exit status should be 0
-
-  Scenario: Subversion Release History in YAML
-    Given a suitable Subversion repository
-    When I run `vclog rel -f yaml`
-    Then the exit status should be 0
-
-  Scenario: Subversion Release History in JSON
-    Given a suitable Subversion repository
-    When I run `vclog rel -f json`
-    Then the exit status should be 0
-

data/test/unit/case_metadata.rb

@@ -1,11 +0,0 @@
-require File.expand_path(File.dirname(__FILE__) + '/helper')
-require 'vclog/metadata'
-
-testcase "VCLog" do
-
-  test "VERSION is set" do
-    ::VCLog::VERSION.assert == File.read('var/version').strip
-  end
-
-end
-

data/test/unit/helper.rb

@@ -1,4 +0,0 @@
-$:.unshift File.expand_path(File.dirname(__FILE__) + '/../../lib')
-
-require 'citron'
-require 'ae'