Jump to: navigation, search

Difference between revisions of "Buckminster SVN Reader"

m (fixing definition list)
 
Line 5: Line 5:
 
<noinclude>
 
<noinclude>
 
=Description=
 
=Description=
The SVN repository reader assumes that any repository contains the three
+
The SVN repository reader assumes that any repository contains the three recommended directories <tt>trunk</tt>, <tt>tags</tt>, and <tt>branches</tt>. A missing <tt>tags</tt> directory is interpreted as no <tt>tags</tt>. A missing <tt>branches</tt> directory is interpreted as no branches. The URL used as the repository identifier must contain the path element <tt>trunk</tt>. Anything that follows the <tt>trunk</tt> element in the path will be considered a <tt>module</tt> path. The repository URL may also contain a query part that in turn may have four different flags:
recommended directories <tt>trunk</tt>, <tt>tags</tt>, and
+
 
<tt>branches</tt>. A missing <tt>tags</tt> directory is
+
; moduleBeforeTag
interpreted as no <tt>tags</tt>. A missing <tt>branches</tt>
+
: When resolving a tag, put the module name between the <code>tags</code> directory and the actual tag
directory is interpreted as no branches. The URL used as the repository
+
; moduleAfterTag
identifier must contain the path element <tt>trunk</tt>. Anything that follows the
+
: When resolving a tag, append the module name after the actual tag
<tt>trunk</tt> element in the path will be considered a
+
; moduleBeforeBranch
<tt>module</tt> path. The repository URL may also contain a query part
+
: When resolving a branch, put the module name between the <code>branches</code> directory and the actual branch
that in turn may have four different flags:
+
; moduleAfterBranch
<dl>
+
: When resolving a branch, append the module name after the actual branch
<dt>moduleBeforeTag</dt>
+
 
<dd>When resolving a tag, put the module name between the <code>tags</code>
+
A fragment in the repository URL will be treated as a sub-module. It will be appended at the end of the resolved URL.
directory and the actual tag</dd>
+
<dt>moduleAfterTag</dt>
+
<dd>When resolving a tag, append the module name after the actual tag</dd>
+
<dt>moduleBeforeBranch</dt>
+
<dd>When resolving a branch, put the module name between the
+
<code>branches</code> directory and the actual branch</dd>
+
<dt>moduleAfterBranch</dt>
+
<dd>When resolving a branch, append the module name after the actual branch</dd>
+
</dl>
+
A fragment in the repository URL will be treated as a sub-module. It will be
+
appended at the end of the resolved URL.
+
  
 
==SVN does not support branch/tag combination==
 
==SVN does not support branch/tag combination==

Latest revision as of 16:50, 6 March 2009

< To: Buckminster Project

Definition

The SVN Component Reader reads Subversion repositories. It relies on the headless part of the Subclipse plugin.

Description

The SVN repository reader assumes that any repository contains the three recommended directories trunk, tags, and branches. A missing tags directory is interpreted as no tags. A missing branches directory is interpreted as no branches. The URL used as the repository identifier must contain the path element trunk. Anything that follows the trunk element in the path will be considered a module path. The repository URL may also contain a query part that in turn may have four different flags:

moduleBeforeTag
When resolving a tag, put the module name between the tags directory and the actual tag
moduleAfterTag
When resolving a tag, append the module name after the actual tag
moduleBeforeBranch
When resolving a branch, put the module name between the branches directory and the actual branch
moduleAfterBranch
When resolving a branch, append the module name after the actual branch

A fragment in the repository URL will be treated as a sub-module. It will be appended at the end of the resolved URL.

SVN does not support branch/tag combination

Subversion cannot combine branch with tag and will use "<default branch>/<tag>" to denote a tag, and "<branch>/LATEST" to denote a branch (these notations are the most common even when branches and tags indeed can be combined).

Fixed Version

When a fixed version selector is needed it is based on the change number.

Plugin Information

Needs the Subclipse headless part. See Getting started with Buckminster for informatin on how to install. Examples needed