Author: hboutemy
Date: Sun May 25 05:58:35 2008
New Revision: 659978
URL: http://svn.apache.org/viewvc?rev=659978&view=rev
Log:
o remove extra spaces
o fixed continuum url
Modified:
maven/scm/trunk/maven-scm-site/src/site/apt/clearcase.apt
maven/scm/trunk/maven-scm-site/src/site/apt/cvs.apt
maven/scm/trunk/maven-scm-site/src/site/apt/guide/new_provider.apt
maven/scm/trunk/maven-scm-site/src/site/apt/index.apt
maven/scm/trunk/maven-scm-site/src/site/apt/perforce.apt
maven/scm/trunk/maven-scm-site/src/site/apt/scm-commands.apt
maven/scm/trunk/maven-scm-site/src/site/apt/scms-overview.apt
maven/scm/trunk/maven-scm-site/src/site/apt/synergy.apt
Modified: maven/scm/trunk/maven-scm-site/src/site/apt/clearcase.apt
URL:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-site/src/site/apt/clearcase.apt?rev=659978&r1=659977&r2=659978&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-site/src/site/apt/clearcase.apt (original)
+++ maven/scm/trunk/maven-scm-site/src/site/apt/clearcase.apt Sun May 25
05:58:35 2008
@@ -22,19 +22,19 @@
-------
scm:clearcase<delimiter>[view_name]<delimiter>config_spec
-------
-
+
<view_name>: Name of the view that is created on a 'checkout' of the code.
This parameter is optional.
<config_spec>: Either
-
+
* a user-supplied config spec file, or
-
+
* one load rule that is used by the ClearCase SCM provider to
automatically generate a config spec when creating a view.
** ClearCase UCM
- If you are using ClearCase UCM, the URL format is the following
-
+ If you are using ClearCase UCM, the URL format is the following
+
-------
scm:clearcase<delimiter>[view_name]<delimiter>config_spec<delimiter>vob_name<delimiter>stream_name
-------
@@ -47,16 +47,16 @@
If you specify the location of an user-supplied config spec file in the SCM
URL, this config spec is used each time
a view is created. SCM URL samples:
-
+
-------
scm:clearcase:\\myserver\clearcase\configspecs\my_module.txt
scm:clearcase:my_module_view:\\myserver\clearcase\configspecs\my_module.txt
-------
-
+
To make sure all the correct elements are loaded in the view, the config
spec must
have "load" rules specified. You can also include other config specs into
your own config spec, as in the following
example:
-
+
-------
include \\myserver\clearcase\configspecs\my_dynamic_configspec.txt
load /myvob/modules/my_module
@@ -70,7 +70,7 @@
(in Continuum, for example, by adjusting the POM file location within the
Build definition).
** Auto-generated config spec
-
+
For many users of a base ClearCase SCM installation, auto-generated config
specs are more convenient than user-supplied
config specs. Instead of being forced to provide a config spec file at an
external location, the SCM URL contains
all information that is needed to check out the code. Specify one load
rule for the project you want to check out within the
@@ -82,7 +82,7 @@
-------
This information is used by the ClearCase SCM provider to automatically
generate the following config spec:
-
+
-------
element * CHECKEDOUT
element * /main/LATEST
@@ -112,17 +112,17 @@
As the view name, the <view_name> parameter is used if it has been
specified. Many users prefer to leave the <view_name> parameter out,
as the ClearCase SCM provider automatically chooses a view name according
to the following pattern:
<username>-<hostname>-maven-<checkoutdir>, e.g.
johndoe-mymachine-maven-myproject.
-
+
Notice that the ClearCase SCM provider does not remove views once they have
been created. When you don't need the view any longer,
remember to explicitly remove it using ClearCase HomeBase or cleartool,
e.g. using one of the following commands:
-
+
-------
cleartool rmview /views/myproject
cleartool rmview -tag johndoe-mymachine-maven-myproject
-------
In case a view name already exists when checking out, ClearCase reports an
error like the following:
-
+
-------
cleartool: Error: A registry entry already exists for
"johndoe-mymachine-maven-myproject".
-------
@@ -151,7 +151,7 @@
This setting is only relevant if and when <<useVWSParameter>> has been
left or set to the default value of <<true>>.
By default the viewstore location <<\\\\${hostname}\viewstore>> is used.
To define another viewstore location,
use the following setting:
-
+
-------
<clearcase-settings>
<viewstore>\\mymachine\myvwstore</viewstore>
@@ -171,7 +171,7 @@
As ClearCase LT uses a predefined and unchangeable folder as the viewstore
directory, you should also specify the viewstore
root location in the clearcase-settings.xml file:
-
+
-------
<clearcase-settings>
<clearcaseType>LT</clearcaseType>
@@ -192,4 +192,3 @@
Notice that this option provides only very limited integration of Maven
into the configuration management system. As no
SCM metadata can be accessed, it is not possible to use SCM plugin
features like creating tags (applying labels), creating changelogs,
and so on.
-
Modified: maven/scm/trunk/maven-scm-site/src/site/apt/cvs.apt
URL:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-site/src/site/apt/cvs.apt?rev=659978&r1=659977&r2=659978&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-site/src/site/apt/cvs.apt (original)
+++ maven/scm/trunk/maven-scm-site/src/site/apt/cvs.apt Sun May 25 05:58:35 2008
@@ -32,7 +32,7 @@
* lserver, connecting to a local server
* pserver, connecting to a password-authenticating server
-
+
* sspi, secure authentication (less supported by clients and servers, may
require using native implementation, for more details see "How to choose the
CVS provider implementation")
* ext, connecting to a server using an external rsh program
@@ -135,4 +135,3 @@
</cvsVariables>
</cvs-settings>
-------
-
Modified: maven/scm/trunk/maven-scm-site/src/site/apt/guide/new_provider.apt
URL:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-site/src/site/apt/guide/new_provider.apt?rev=659978&r1=659977&r2=659978&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-site/src/site/apt/guide/new_provider.apt
(original)
+++ maven/scm/trunk/maven-scm-site/src/site/apt/guide/new_provider.apt Sun May
25 05:58:35 2008
@@ -136,7 +136,7 @@
{
MyScmProviderRepository providerRepository = new
MyScmProviderRepository();
//Parse scmSpecificUrl and populate there your provider repository
-
+
return providerRepository;
}
}
Modified: maven/scm/trunk/maven-scm-site/src/site/apt/index.apt
URL:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-site/src/site/apt/index.apt?rev=659978&r1=659977&r2=659978&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-site/src/site/apt/index.apt (original)
+++ maven/scm/trunk/maven-scm-site/src/site/apt/index.apt Sun May 25 05:58:35
2008
@@ -10,7 +10,7 @@
Maven SCM supports Maven 2.x plugins (e.g.
{{{http://maven.apache.org/plugins/maven-release-plugin/}maven-release-plugin}})
- and other tools (e.g.
{{{http://maven.apache.org/continuum/index.html}Continuum}})
+ and other tools (e.g. {{{http://continuum.apache.org/}Continuum}})
by providing them with a common API for doing SCM operations. You can look at
{{{scms-overview.html}the list of SCM's}} for more information on using
Maven SCM with your favorite SCM tool.
Modified: maven/scm/trunk/maven-scm-site/src/site/apt/perforce.apt
URL:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-site/src/site/apt/perforce.apt?rev=659978&r1=659977&r2=659978&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-site/src/site/apt/perforce.apt (original)
+++ maven/scm/trunk/maven-scm-site/src/site/apt/perforce.apt Sun May 25
05:58:35 2008
@@ -42,5 +42,3 @@
*--------------------------------+----------+-------------------+------------------------------------------+
| maven.scm.jobs |properties|word, The job name | Job name
|
*--------------------------------+----------+-------------------+------------------------------------------+
-
-
Modified: maven/scm/trunk/maven-scm-site/src/site/apt/scm-commands.apt
URL:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-site/src/site/apt/scm-commands.apt?rev=659978&r1=659977&r2=659978&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-site/src/site/apt/scm-commands.apt (original)
+++ maven/scm/trunk/maven-scm-site/src/site/apt/scm-commands.apt Sun May 25
05:58:35 2008
@@ -10,42 +10,42 @@
Maven SCM uses a exposes a fixed set of commands for it users. The providers
for each SCM must implements those commands through
the ScmProvider interface. This is an overview of all the commands:
-
+
* Add
Adds a new file to the source control system
-
+
* Changelog
Produces a list of changed (a new version has been put in the system)
files. This list can then be used to display the latest changes
or the developer(s) who did the latest changes.
-
+
* Checkin
Save the changes you have done into the repository. This will create a new
version of the file or
directory in the repository.
-
+
* Checkout
Copy (part of) the contents of the source control system to a certain
location on your local machine. It should be possible to scm operations in that
location.
-
+
* Edit
Mark a file as editable with the source control system. This is used in
source control systems where you look at read-only files
and you need to make them not read-only anymore before you can edit them.
In some scm's this means that no other user can then do an edit at the same
time.
-
+
* Diff
TODO
-
+
* Remove
Removes a file from the source control system
-
+
* Status
Gives a list of files that still need some source control operation (files
that still need to be added, files that are in edit mode, ...)
-
+
* Tag
Tags (label in some scm's) a source tree with a certain tag. This allows to
make reproducable builds later by checking out the source code that has this
tag.
@@ -53,4 +53,3 @@
* Update
Updates the checkout'ed source code to the latest state in the source
control repository.
-
Modified: maven/scm/trunk/maven-scm-site/src/site/apt/scms-overview.apt
URL:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-site/src/site/apt/scms-overview.apt?rev=659978&r1=659977&r2=659978&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-site/src/site/apt/scms-overview.apt (original)
+++ maven/scm/trunk/maven-scm-site/src/site/apt/scms-overview.apt Sun May 25
05:58:35 2008
@@ -65,5 +65,3 @@
* Svk
* Vesta
-
-
Modified: maven/scm/trunk/maven-scm-site/src/site/apt/synergy.apt
URL:
http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-site/src/site/apt/synergy.apt?rev=659978&r1=659977&r2=659978&view=diff
==============================================================================
--- maven/scm/trunk/maven-scm-site/src/site/apt/synergy.apt (original)
+++ maven/scm/trunk/maven-scm-site/src/site/apt/synergy.apt Sun May 25 05:58:35
2008
@@ -21,7 +21,7 @@
-------
scm:synergy<delimiter>project_name<delimiter>database_delimiter<delimiter>project_version<delimiter>release<delimiter>purpose
-------
-
+
<project_name>: This is the name of the project from which the checkout is
done.
<project_version>: This is the version of the project from which the
checkout is done (usually a prep project).
@@ -44,11 +44,11 @@
Checkout purpose is to get sources from a working Work Area to a given
folder. First,
it checks if a work area already exists with the given version. If yes, it
only synchronizes and reconfigures
the existing one, and then copies file to the expecting folder. If no Work
Area exists, then a checkout is done.
-
+
To specify the version of the checkout working project, use <tag>
parameter.
-
+
When a 'checkout' happens, the following scm commands are generated
-
+
-------
ccm start -m -q -nogui -n <username> -pw <password>
ccm query -u -f %displayname "owner='<username>' and status='working' and
type='project' and has_predecessor('<project_spec>:project:1')" //Check for
existing checkout
@@ -103,7 +103,7 @@
* maven.scm.synergy.country (default value is US)
[]
-
+
-------
ccm start -m -q -nogui -n <username> -pw <password>
ccm query -u
is_task_in_folder_of(is_folder_in_rp_of('<project_spec>:project:1')) and
completion_date>time(<startDate>) and completion_date<time(<endDate>)
