vclog 1.8.1 → 1.8.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/.ruby +57 -0
- data/COPYING.rdoc +32 -0
- data/README.rdoc +18 -19
- data/features/git.feature +16 -16
- data/features/hg.feature +16 -16
- data/features/step_definitions/repo_steps.rb +2 -1
- data/features/support/aruba.rb +5 -1
- data/features/support/repo.rb +7 -3
- data/features/svn.feature +16 -16
- data/lib/vclog.rb +1 -1
- data/lib/vclog/adapters/abstract.rb +0 -19
- data/lib/vclog/adapters/git.rb +34 -6
- data/lib/vclog/adapters/svn.rb +1 -1
- data/lib/vclog/change.rb +43 -23
- data/lib/vclog/heuristics.rb +32 -49
- data/lib/vclog/heuristics/label.rb +29 -0
- data/lib/vclog/heuristics/rule.rb +33 -0
- data/lib/vclog/metadata.rb +2 -12
- data/lib/vclog/repo.rb +23 -19
- data/{ronn → man/man1}/index.txt +0 -0
- data/man/man1/vclog-autotag.1.html +117 -0
- data/{ronn/vclog-autotag.ronn → man/man1/vclog-autotag.1.ronn} +0 -0
- data/man/man1/vclog-bump.1.html +111 -0
- data/{ronn/vclog-bump.ronn → man/man1/vclog-bump.1.ronn} +0 -0
- data/man/man1/vclog-changelog.1.html +123 -0
- data/{ronn/vclog-changelog.ronn → man/man1/vclog-changelog.1.ronn} +0 -0
- data/man/man1/vclog-history.1.html +122 -0
- data/{ronn/vclog-history.ronn → man/man1/vclog-history.1.ronn} +0 -0
- data/man/man1/vclog-version.1.html +100 -0
- data/{ronn/vclog-version.ronn → man/man1/vclog-version.1.ronn} +0 -0
- data/man/man1/vclog.1.html +122 -0
- data/{ronn/vclog.ronn → man/man1/vclog.1.ronn} +0 -0
- data/test/unit/case_metadata.rb +11 -0
- data/test/unit/helper.rb +4 -0
- metadata +132 -122
- data/HISTORY.rdoc +0 -158
- data/LICENSE +0 -203
- data/lib/plugins/syckle/vclog.rb +0 -221
- data/lib/vclog/heuristics/default.rb +0 -24
- data/lib/vclog/meta/data.rb +0 -25
- data/lib/vclog/meta/package +0 -11
- data/lib/vclog/meta/profile +0 -18
- data/meta/data.rb +0 -25
- data/meta/package +0 -11
- data/meta/profile +0 -18
data/.ruby
ADDED
@@ -0,0 +1,57 @@
|
|
1
|
+
---
|
2
|
+
source:
|
3
|
+
- profile
|
4
|
+
authors:
|
5
|
+
- name: Trans
|
6
|
+
email: transfire@gmail.com
|
7
|
+
copyrights:
|
8
|
+
- holder: Rubyworks
|
9
|
+
year: '2009'
|
10
|
+
license: BSD-2-Clause
|
11
|
+
replacements: []
|
12
|
+
alternatives: []
|
13
|
+
requirements:
|
14
|
+
- name: facets
|
15
|
+
version: 2.4+
|
16
|
+
- name: ansi
|
17
|
+
version: 1.2+
|
18
|
+
- name: confection
|
19
|
+
- name: xml-simple
|
20
|
+
- name: detroit
|
21
|
+
groups:
|
22
|
+
- build
|
23
|
+
development: true
|
24
|
+
- name: citron
|
25
|
+
groups:
|
26
|
+
- test
|
27
|
+
development: true
|
28
|
+
- name: ae
|
29
|
+
groups:
|
30
|
+
- test
|
31
|
+
development: true
|
32
|
+
- name: cucumber
|
33
|
+
groups:
|
34
|
+
- test
|
35
|
+
development: true
|
36
|
+
- name: aruba
|
37
|
+
groups:
|
38
|
+
- test
|
39
|
+
development: true
|
40
|
+
dependencies: []
|
41
|
+
conflicts: []
|
42
|
+
repositories: []
|
43
|
+
resources:
|
44
|
+
home: http://rubyworks.github.com/vclog
|
45
|
+
code: http://github.com/rubyworks/vclog
|
46
|
+
extra: {}
|
47
|
+
load_path:
|
48
|
+
- lib
|
49
|
+
revision: 0
|
50
|
+
created: '2006-05-09'
|
51
|
+
summary: Cross-VCS/SCM ChangeLog Generator
|
52
|
+
title: VCLog
|
53
|
+
version: 1.8.2
|
54
|
+
name: vclog
|
55
|
+
description: VCLog is a cross-VCS/SCM ChangeLog generator.
|
56
|
+
organization: Rubyworks
|
57
|
+
date: '2011-11-07'
|
data/COPYING.rdoc
ADDED
@@ -0,0 +1,32 @@
|
|
1
|
+
= COPYRIGHT NOTICES
|
2
|
+
|
3
|
+
== VCLog
|
4
|
+
|
5
|
+
Copyright:: (c) 2008 Rubyworks
|
6
|
+
License:: BSD-2-Clause
|
7
|
+
Website:: http://rubyworks.github.com/vclog
|
8
|
+
|
9
|
+
Copyright 2008 Rubyworks. All rights reserved.
|
10
|
+
|
11
|
+
Redistribution and use in source and binary forms, with or without
|
12
|
+
modification, are permitted provided that the following conditions are met:
|
13
|
+
|
14
|
+
1. Redistributions of source code must retain the above copyright notice,
|
15
|
+
this list of conditions and the following disclaimer.
|
16
|
+
|
17
|
+
2. Redistributions in binary form must reproduce the above copyright
|
18
|
+
notice, this list of conditions and the following disclaimer in the
|
19
|
+
documentation and/or other materials provided with the distribution.
|
20
|
+
|
21
|
+
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
|
22
|
+
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
|
23
|
+
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
|
24
|
+
COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
|
25
|
+
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
|
26
|
+
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
27
|
+
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
|
28
|
+
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
|
29
|
+
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
|
30
|
+
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
31
|
+
|
32
|
+
|
data/README.rdoc
CHANGED
@@ -1,13 +1,15 @@
|
|
1
1
|
= VCLog
|
2
2
|
|
3
|
-
|
4
|
-
|
5
|
-
|
3
|
+
{Homepage}[http://rubyworks.github.com/vclog] |
|
4
|
+
{Source Code}[http://github.com/rubyworks/vclog] |
|
5
|
+
{Mailing List}[http://googlegroups.com/group/rubyworks-mailinglist]
|
6
|
+
|
7
|
+
{<img src="http://travis-ci.org/rubyworks/vclog.png" />}[http://travis-ci.org/rubyworks/vclog]
|
6
8
|
|
7
9
|
|
8
10
|
== DESCRIPTION
|
9
11
|
|
10
|
-
VCLog is a
|
12
|
+
VCLog is a versatile cross-VCS/SCM changelog generator.
|
11
13
|
It currently supports Git, Hg and (limited) Subversion.
|
12
14
|
|
13
15
|
|
@@ -15,7 +17,7 @@ It currently supports Git, Hg and (limited) Subversion.
|
|
15
17
|
|
16
18
|
=== Creating Changelogs
|
17
19
|
|
18
|
-
The default output is
|
20
|
+
The default output is an ANSI colored GNU-like changelog.
|
19
21
|
From a repository's root directory try:
|
20
22
|
|
21
23
|
$ vclog
|
@@ -34,7 +36,7 @@ To get a release history specify 'history' or 'release' as the subcommand.
|
|
34
36
|
|
35
37
|
$ vclog history
|
36
38
|
|
37
|
-
Again the default format is
|
39
|
+
Again the default format is an ANSI colored GNU-like text style.
|
38
40
|
|
39
41
|
Unlike Changelogs, Histories group changes by tags. The tag message is
|
40
42
|
used as the release note. If the underlying SCM doesn't support
|
@@ -62,8 +64,12 @@ level only bump the patch level.
|
|
62
64
|
|
63
65
|
=== Writing Heuristics
|
64
66
|
|
65
|
-
|
66
|
-
|
67
|
+
You can create custom heuristics for your project in a vclog configuration
|
68
|
+
file. VCLog will look for a `.vclog` file or a `vclog` file in `.config/`,
|
69
|
+
`config/`, `task/` or tasks/` directory (the file can optionally end in `.rb`).
|
70
|
+
|
71
|
+
In the file you define rules in Ruby script for labeling commits based
|
72
|
+
on the commit message.
|
67
73
|
|
68
74
|
on /updated? (README|VERSION|MANIFEST)/ do
|
69
75
|
:admin
|
@@ -81,7 +87,7 @@ the rules.rb to specify the level and description of a commit label.
|
|
81
87
|
set :admin, -2, "Administrative Adjustment"
|
82
88
|
|
83
89
|
|
84
|
-
== NOTE ABOUT
|
90
|
+
== NOTE ABOUT SUBVERSION
|
85
91
|
|
86
92
|
Because Subversion is a centralized version control system, it contacts
|
87
93
|
the server every time 'svn log' is run. For this reason, having vclog
|
@@ -98,17 +104,10 @@ Please see HISTORY file.
|
|
98
104
|
|
99
105
|
== COPYRIGHTS
|
100
106
|
|
101
|
-
Copyright (c)
|
107
|
+
Copyright (c) 2008 Rubyworks
|
102
108
|
|
103
|
-
|
104
|
-
you may not use this file except in compliance with the License.
|
105
|
-
You may obtain a copy of the License at
|
109
|
+
VCLog is distributable in accordance with the terms of the BSD-2-Clause license.
|
106
110
|
|
107
|
-
|
111
|
+
See COPYING.rdoc for details.
|
108
112
|
|
109
|
-
Unless required by applicable law or agreed to in writing, software
|
110
|
-
distributed under the License is distributed on an "AS IS" BASIS,
|
111
|
-
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
112
|
-
See the License for the specific language governing permissions and
|
113
|
-
limitations under the License.
|
114
113
|
|
data/features/git.feature
CHANGED
@@ -5,82 +5,82 @@ Feature: Git Support
|
|
5
5
|
|
6
6
|
Scenario: Git Changelog
|
7
7
|
Given a suitable Git repository
|
8
|
-
When I run
|
8
|
+
When I run `vclog`
|
9
9
|
Then the exit status should be 0
|
10
10
|
|
11
11
|
Scenario: Git Changelog in RDoc
|
12
12
|
Given a suitable Git repository
|
13
|
-
When I run
|
13
|
+
When I run `vclog -f rdoc`
|
14
14
|
Then the exit status should be 0
|
15
15
|
|
16
16
|
Scenario: Git Changelog in Markdown
|
17
17
|
Given a suitable Git repository
|
18
|
-
When I run
|
18
|
+
When I run `vclog -f markdown`
|
19
19
|
Then the exit status should be 0
|
20
20
|
|
21
21
|
Scenario: Git Changelog in HTML
|
22
22
|
Given a suitable Git repository
|
23
|
-
When I run
|
23
|
+
When I run `vclog -f html`
|
24
24
|
Then the exit status should be 0
|
25
25
|
|
26
26
|
Scenario: Git Changelog in XML
|
27
27
|
Given a suitable Git repository
|
28
|
-
When I run
|
28
|
+
When I run `vclog -f xml`
|
29
29
|
Then the exit status should be 0
|
30
30
|
|
31
31
|
Scenario: Git Changelog in Atom
|
32
32
|
Given a suitable Git repository
|
33
|
-
When I run
|
33
|
+
When I run `vclog -f atom`
|
34
34
|
Then the exit status should be 0
|
35
35
|
|
36
36
|
Scenario: Git Changelog in YAML
|
37
37
|
Given a suitable Git repository
|
38
|
-
When I run
|
38
|
+
When I run `vclog -f yaml`
|
39
39
|
Then the exit status should be 0
|
40
40
|
|
41
41
|
Scenario: Git Changelog in JSON
|
42
42
|
Given a suitable Git repository
|
43
|
-
When I run
|
43
|
+
When I run `vclog -f json`
|
44
44
|
Then the exit status should be 0
|
45
45
|
|
46
46
|
|
47
47
|
Scenario: Git Release History
|
48
48
|
Given a suitable Git repository
|
49
|
-
When I run
|
49
|
+
When I run `vclog r`
|
50
50
|
Then the exit status should be 0
|
51
51
|
|
52
52
|
Scenario: Git Release History in RDoc
|
53
53
|
Given a suitable Git repository
|
54
|
-
When I run
|
54
|
+
When I run `vclog r -f rdoc`
|
55
55
|
Then the exit status should be 0
|
56
56
|
|
57
57
|
Scenario: Git Release History in Markdown
|
58
58
|
Given a suitable Git repository
|
59
|
-
When I run
|
59
|
+
When I run `vclog rel -f markdown`
|
60
60
|
Then the exit status should be 0
|
61
61
|
|
62
62
|
Scenario: Git Release History in HTML
|
63
63
|
Given a suitable Git repository
|
64
|
-
When I run
|
64
|
+
When I run `vclog rel -f html`
|
65
65
|
Then the exit status should be 0
|
66
66
|
|
67
67
|
Scenario: Git Release History in XML
|
68
68
|
Given a suitable Git repository
|
69
|
-
When I run
|
69
|
+
When I run `vclog rel -f xml`
|
70
70
|
Then the exit status should be 0
|
71
71
|
|
72
72
|
Scenario: Git Release History in Atom
|
73
73
|
Given a suitable Git repository
|
74
|
-
When I run
|
74
|
+
When I run `vclog rel -f atom`
|
75
75
|
Then the exit status should be 0
|
76
76
|
|
77
77
|
Scenario: Git Release History in YAML
|
78
78
|
Given a suitable Git repository
|
79
|
-
When I run
|
79
|
+
When I run `vclog rel -f yaml`
|
80
80
|
Then the exit status should be 0
|
81
81
|
|
82
82
|
Scenario: Git Release History in JSON
|
83
83
|
Given a suitable Git repository
|
84
|
-
When I run
|
84
|
+
When I run `vclog rel -f json`
|
85
85
|
Then the exit status should be 0
|
86
86
|
|
data/features/hg.feature
CHANGED
@@ -5,82 +5,82 @@ Feature: Mercurial Support
|
|
5
5
|
|
6
6
|
Scenario: Mercurial Changelog
|
7
7
|
Given a suitable Mercurial repository
|
8
|
-
When I run
|
8
|
+
When I run `vclog`
|
9
9
|
Then the exit status should be 0
|
10
10
|
|
11
11
|
Scenario: Mercurial Changelog in RDoc
|
12
12
|
Given a suitable Mercurial repository
|
13
|
-
When I run
|
13
|
+
When I run `vclog -f rdoc`
|
14
14
|
Then the exit status should be 0
|
15
15
|
|
16
16
|
Scenario: Mercurial Changelog in Markdown
|
17
17
|
Given a suitable Mercurial repository
|
18
|
-
When I run
|
18
|
+
When I run `vclog -f markdown`
|
19
19
|
Then the exit status should be 0
|
20
20
|
|
21
21
|
Scenario: Mercurial Changelog in HTML
|
22
22
|
Given a suitable Mercurial repository
|
23
|
-
When I run
|
23
|
+
When I run `vclog -f html`
|
24
24
|
Then the exit status should be 0
|
25
25
|
|
26
26
|
Scenario: Mercurial Changelog in XML
|
27
27
|
Given a suitable Mercurial repository
|
28
|
-
When I run
|
28
|
+
When I run `vclog -f xml`
|
29
29
|
Then the exit status should be 0
|
30
30
|
|
31
31
|
Scenario: Mercurial Changelog in Atom
|
32
32
|
Given a suitable Mercurial repository
|
33
|
-
When I run
|
33
|
+
When I run `vclog -f atom`
|
34
34
|
Then the exit status should be 0
|
35
35
|
|
36
36
|
Scenario: Mercurial Changelog in YAML
|
37
37
|
Given a suitable Mercurial repository
|
38
|
-
When I run
|
38
|
+
When I run `vclog -f yaml`
|
39
39
|
Then the exit status should be 0
|
40
40
|
|
41
41
|
Scenario: Mercurial Changelog in JSON
|
42
42
|
Given a suitable Mercurial repository
|
43
|
-
When I run
|
43
|
+
When I run `vclog -f json`
|
44
44
|
Then the exit status should be 0
|
45
45
|
|
46
46
|
|
47
47
|
Scenario: Mercurial Release History
|
48
48
|
Given a suitable Mercurial repository
|
49
|
-
When I run
|
49
|
+
When I run `vclog rel`
|
50
50
|
Then the exit status should be 0
|
51
51
|
|
52
52
|
Scenario: Mercurial Release History in RDoc
|
53
53
|
Given a suitable Mercurial repository
|
54
|
-
When I run
|
54
|
+
When I run `vclog rel -f rdoc`
|
55
55
|
Then the exit status should be 0
|
56
56
|
|
57
57
|
Scenario: Mercurial Release History in Markdown
|
58
58
|
Given a suitable Mercurial repository
|
59
|
-
When I run
|
59
|
+
When I run `vclog rel -f markdown`
|
60
60
|
Then the exit status should be 0
|
61
61
|
|
62
62
|
Scenario: Mercurial Release History in HTML
|
63
63
|
Given a suitable Mercurial repository
|
64
|
-
When I run
|
64
|
+
When I run `vclog rel -f html`
|
65
65
|
Then the exit status should be 0
|
66
66
|
|
67
67
|
Scenario: Mercurial Release History in XML
|
68
68
|
Given a suitable Mercurial repository
|
69
|
-
When I run
|
69
|
+
When I run `vclog rel -f xml`
|
70
70
|
Then the exit status should be 0
|
71
71
|
|
72
72
|
Scenario: Mercurial Release History in Atom
|
73
73
|
Given a suitable Mercurial repository
|
74
|
-
When I run
|
74
|
+
When I run `vclog rel -f atom`
|
75
75
|
Then the exit status should be 0
|
76
76
|
|
77
77
|
Scenario: Mercurial Release History in YAML
|
78
78
|
Given a suitable Mercurial repository
|
79
|
-
When I run
|
79
|
+
When I run `vclog rel -f yaml`
|
80
80
|
Then the exit status should be 0
|
81
81
|
|
82
82
|
Scenario: Mercurial Release History in JSON
|
83
83
|
Given a suitable Mercurial repository
|
84
|
-
When I run
|
84
|
+
When I run `vclog rel -f json`
|
85
85
|
Then the exit status should be 0
|
86
86
|
|
@@ -18,7 +18,7 @@ Given /a suitable Subversion repository/ do
|
|
18
18
|
end
|
19
19
|
|
20
20
|
Given /a suitable Git repository/ do
|
21
|
-
url = "git://github.com/
|
21
|
+
url = "git://github.com/rubyworks/vclog.git"
|
22
22
|
name = "vclog"
|
23
23
|
type = "git"
|
24
24
|
marker = ".git"
|
@@ -53,6 +53,7 @@ Given /a suitable Mercurial repository/ do
|
|
53
53
|
#cd(name)
|
54
54
|
end
|
55
55
|
|
56
|
+
# TODO
|
56
57
|
Given /a suitable Darcs repository/ do
|
57
58
|
url =
|
58
59
|
name =
|
data/features/support/aruba.rb
CHANGED
data/features/support/repo.rb
CHANGED
@@ -1,6 +1,7 @@
|
|
1
1
|
#
|
2
2
|
def setup_repo(name, type, marker, clone_command)
|
3
3
|
dir = File.expand_path("tmp/hold/#{type}")
|
4
|
+
dst = File.expand_path("tmp/aruba")
|
4
5
|
|
5
6
|
unless File.exist?("#{dir}/#{name}/#{marker}")
|
6
7
|
$stderr.puts(" #{clone_command}")
|
@@ -8,8 +9,11 @@ def setup_repo(name, type, marker, clone_command)
|
|
8
9
|
`cd #{dir}; #{clone_command}`
|
9
10
|
end
|
10
11
|
|
11
|
-
|
12
|
-
|
13
|
-
|
12
|
+
#unless File.exist?("tmp/aruba/#{type}/#{name}")
|
13
|
+
`mkdir -p #{dst}`
|
14
|
+
`cp -r #{dir} #{dst}/#{type}/`
|
15
|
+
#end
|
16
|
+
|
17
|
+
cd("#{type}/#{name}")
|
14
18
|
end
|
15
19
|
|
data/features/svn.feature
CHANGED
@@ -5,82 +5,82 @@ Feature: Subversion Support
|
|
5
5
|
|
6
6
|
Scenario: Subversion Changelog
|
7
7
|
Given a suitable Subversion repository
|
8
|
-
When I run
|
8
|
+
When I run `vclog`
|
9
9
|
Then the exit status should be 0
|
10
10
|
|
11
11
|
Scenario: Subversion Changelog in RDoc
|
12
12
|
Given a suitable Subversion repository
|
13
|
-
When I run
|
13
|
+
When I run `vclog -f rdoc`
|
14
14
|
Then the exit status should be 0
|
15
15
|
|
16
16
|
Scenario: Subversion Changelog in Markdown
|
17
17
|
Given a suitable Subversion repository
|
18
|
-
When I run
|
18
|
+
When I run `vclog -f markdown`
|
19
19
|
Then the exit status should be 0
|
20
20
|
|
21
21
|
Scenario: Subversion Changelog in HTML
|
22
22
|
Given a suitable Subversion repository
|
23
|
-
When I run
|
23
|
+
When I run `vclog -f html`
|
24
24
|
Then the exit status should be 0
|
25
25
|
|
26
26
|
Scenario: Subversion Changelog in XML
|
27
27
|
Given a suitable Subversion repository
|
28
|
-
When I run
|
28
|
+
When I run `vclog -f xml`
|
29
29
|
Then the exit status should be 0
|
30
30
|
|
31
31
|
Scenario: Subversion Changelog in Atom
|
32
32
|
Given a suitable Subversion repository
|
33
|
-
When I run
|
33
|
+
When I run `vclog -f atom`
|
34
34
|
Then the exit status should be 0
|
35
35
|
|
36
36
|
Scenario: Subversion Changelog in YAML
|
37
37
|
Given a suitable Subversion repository
|
38
|
-
When I run
|
38
|
+
When I run `vclog -f yaml`
|
39
39
|
Then the exit status should be 0
|
40
40
|
|
41
41
|
Scenario: Subversion Changelog in JSON
|
42
42
|
Given a suitable Subversion repository
|
43
|
-
When I run
|
43
|
+
When I run `vclog -f json`
|
44
44
|
Then the exit status should be 0
|
45
45
|
|
46
46
|
|
47
47
|
Scenario: Subversion Release History
|
48
48
|
Given a suitable Subversion repository
|
49
|
-
When I run
|
49
|
+
When I run `vclog rel`
|
50
50
|
Then the exit status should be 0
|
51
51
|
|
52
52
|
Scenario: Subversion Release History in RDoc
|
53
53
|
Given a suitable Subversion repository
|
54
|
-
When I run
|
54
|
+
When I run `vclog rel -f rdoc`
|
55
55
|
Then the exit status should be 0
|
56
56
|
|
57
57
|
Scenario: Subversion Release History in Markdown
|
58
58
|
Given a suitable Subversion repository
|
59
|
-
When I run
|
59
|
+
When I run `vclog rel -f markdown`
|
60
60
|
Then the exit status should be 0
|
61
61
|
|
62
62
|
Scenario: Subversion Release History in HTML
|
63
63
|
Given a suitable Subversion repository
|
64
|
-
When I run
|
64
|
+
When I run `vclog rel -f html`
|
65
65
|
Then the exit status should be 0
|
66
66
|
|
67
67
|
Scenario: Subversion Release History in XML
|
68
68
|
Given a suitable Subversion repository
|
69
|
-
When I run
|
69
|
+
When I run `vclog rel -f xml`
|
70
70
|
Then the exit status should be 0
|
71
71
|
|
72
72
|
Scenario: Subversion Release History in Atom
|
73
73
|
Given a suitable Subversion repository
|
74
|
-
When I run
|
74
|
+
When I run `vclog rel -f atom`
|
75
75
|
Then the exit status should be 0
|
76
76
|
|
77
77
|
Scenario: Subversion Release History in YAML
|
78
78
|
Given a suitable Subversion repository
|
79
|
-
When I run
|
79
|
+
When I run `vclog rel -f yaml`
|
80
80
|
Then the exit status should be 0
|
81
81
|
|
82
82
|
Scenario: Subversion Release History in JSON
|
83
83
|
Given a suitable Subversion repository
|
84
|
-
When I run
|
84
|
+
When I run `vclog rel -f json`
|
85
85
|
Then the exit status should be 0
|
86
86
|
|