vclog 1.8.1 → 1.8.2

data/.ruby

@@ -0,0 +1,57 @@
+---
+source:
+- profile
+authors:
+- name: Trans
+  email: transfire@gmail.com
+copyrights:
+- holder: Rubyworks
+  year: '2009'
+  license: BSD-2-Clause
+replacements: []
+alternatives: []
+requirements:
+- name: facets
+  version: 2.4+
+- name: ansi
+  version: 1.2+
+- name: confection
+- name: xml-simple
+- name: detroit
+  groups:
+  - build
+  development: true
+- name: citron
+  groups:
+  - test
+  development: true
+- name: ae
+  groups:
+  - test
+  development: true
+- name: cucumber
+  groups:
+  - test
+  development: true
+- name: aruba
+  groups:
+  - test
+  development: true
+dependencies: []
+conflicts: []
+repositories: []
+resources:
+  home: http://rubyworks.github.com/vclog
+  code: http://github.com/rubyworks/vclog
+extra: {}
+load_path:
+- lib
+revision: 0
+created: '2006-05-09'
+summary: Cross-VCS/SCM ChangeLog Generator
+title: VCLog
+version: 1.8.2
+name: vclog
+description: VCLog is a cross-VCS/SCM ChangeLog generator.
+organization: Rubyworks
+date: '2011-11-07'

data/COPYING.rdoc

@@ -0,0 +1,32 @@
+= 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/README.rdoc

@@ -1,13 +1,15 @@
 = VCLog
 
-* home: http://rubyworks.github.com/vclog
-* code: http://github.com/rubyworks/vclog
-* talk: http://googlegroups.com/group/rubyworks-mailinglist
+{Homepage}[http://rubyworks.github.com/vclog] |
+{Source Code}[http://github.com/rubyworks/vclog] |
+{Mailing List}[http://googlegroups.com/group/rubyworks-mailinglist]
+
+{<img src="http://travis-ci.org/rubyworks/vclog.png" />}[http://travis-ci.org/rubyworks/vclog]
 
 
 == DESCRIPTION
 
-VCLog is a versitle cross-VCS/SCM changelog generator.
+VCLog is a versatile cross-VCS/SCM changelog generator.
 It currently supports Git, Hg and (limited) Subversion.
 
 
@@ -15,7 +17,7 @@ It currently supports Git, Hg and (limited) Subversion.
 
 === Creating Changelogs
 
-The default output is a ANSI colored GNU-like changelog.
+The default output is an ANSI colored GNU-like changelog.
 From a repository's root directory try:
 
   $ vclog
@@ -34,7 +36,7 @@ To get a release history specify 'history' or 'release' as the subcommand.
 
   $ vclog history
 
-Again the default format is a ANSI colored GNU-like text style.
+Again the default format is an ANSI colored GNU-like text style.
 
 Unlike Changelogs, Histories group changes by tags. The tag message is
 used as the release note. If the underlying SCM doesn't support 
@@ -62,8 +64,12 @@ level only bump the patch level.
 
 === Writing Heuristics
 
-In your projects .vclog/rules.rb or .config/vclog/rules.rb file, you
-can create rules for labeling commit messages bassed on commit message.
+You can create custom heuristics for your project in a vclog configuration
+file. VCLog will look for a `.vclog` file or a `vclog` file in `.config/`,
+`config/`, `task/` or tasks/` directory (the file can optionally end in `.rb`).
+
+In the file you define rules in Ruby script for labeling commits based
+on the commit message.
 
   on /updated? (README|VERSION|MANIFEST)/ do
     :admin
@@ -81,7 +87,7 @@ the rules.rb to specify the level and description of a commit label.
   set :admin, -2, "Administrative Adjustment"
 
 
-== NOTE ABOUT SUBVSERION
+== NOTE ABOUT SUBVERSION
 
 Because Subversion is a centralized version control system, it contacts
 the server every time 'svn log' is run. For this reason, having vclog
@@ -98,17 +104,10 @@ Please see HISTORY file.
 
 == COPYRIGHTS
 
-Copyright (c) 2009 Thomas Sawyer
+Copyright (c) 2008 Rubyworks
 
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
+VCLog is distributable in accordance with the terms of the BSD-2-Clause license.
 
-   http://www.apache.org/licenses/LICENSE-2.0
+See COPYING.rdoc for details.
 
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
 

data/features/git.feature

@@ -5,82 +5,82 @@ Feature: Git Support
 
   Scenario: Git Changelog
     Given a suitable Git repository
-    When I run "vclog"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    When I run `vclog rel -f json`
     Then the exit status should be 0
 

data/features/hg.feature

@@ -5,82 +5,82 @@ Feature: Mercurial Support
 
   Scenario: Mercurial Changelog
     Given a suitable Mercurial repository
-    When I run "vclog"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    When I run `vclog rel -f json`
     Then the exit status should be 0
 

data/features/step_definitions/repo_steps.rb

@@ -18,7 +18,7 @@ Given /a suitable Subversion repository/ do
 end
 
 Given /a suitable Git repository/ do
-  url    = "git://github.com/proutils/vclog.git"
+  url    = "git://github.com/rubyworks/vclog.git"
   name   = "vclog"
   type   = "git"
   marker = ".git"
@@ -53,6 +53,7 @@ Given /a suitable Mercurial repository/ do
   #cd(name)
 end
 
+# TODO
 Given /a suitable Darcs repository/ do
   url  = 
   name = 

data/features/support/aruba.rb

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

data/features/support/repo.rb

@@ -1,6 +1,7 @@
 #
 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}")
@@ -8,8 +9,11 @@ def setup_repo(name, type, marker, clone_command)
     `cd #{dir}; #{clone_command}`
   end
 
-  run "cp -r #{dir} #{type}"
-  cd(type)
-  cd(name)
+  #unless File.exist?("tmp/aruba/#{type}/#{name}")
+    `mkdir -p #{dst}`
+    `cp -r #{dir} #{dst}/#{type}/`
+  #end
+
+  cd("#{type}/#{name}")
 end
 

data/features/svn.feature

@@ -5,82 +5,82 @@ Feature: Subversion Support
 
   Scenario: Subversion Changelog
     Given a suitable Subversion repository
-    When I run "vclog"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    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"
+    When I run `vclog rel -f json`
     Then the exit status should be 0