9
~~ Licensed to the Apache Software Foundation (ASF) under one
10
~~ or more contributor license agreements. See the NOTICE file
11
~~ distributed with this work for additional information
12
~~ regarding copyright ownership. The ASF licenses this file
13
~~ to you under the Apache License, Version 2.0 (the
14
~~ "License"); you may not use this file except in compliance
15
~~ with the License. You may obtain a copy of the License at
17
~~ http://www.apache.org/licenses/LICENSE-2.0
19
~~ Unless required by applicable law or agreed to in writing,
20
~~ software distributed under the License is distributed on an
21
~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
22
~~ KIND, either express or implied. See the License for the
23
~~ specific language governing permissions and limitations
26
~~ NOTE: For help with the syntax of this file, see:
27
~~ http://maven.apache.org/doxia/references/apt-format.html
31
You need to add some extensions
32
(wagon-scm, maven-scm-manager-plexus and the maven-scm-provider for your SCM system, see examples below)
33
to your pom and use URLs in the
34
{{{http://maven.apache.org/scm/scm-url-format.html}SCM format}}.
36
For non-subversion SCM, in your settings.xml file you can include the elements <<<scmVersionType>>> and <<<scmVersion>>> to
37
specify a branch or tag to use. The value of <<<scmVersionType>>> must be one of <<<branch>>> or <<<tag>>>.
38
There is no default value for <<<scmVersionType>>> so you <MUST> specify it with <<<scmVersion>>> in order
42
Deploying your Maven site to Subversion
44
Add the following extensions to your pom and use a wagon-scm url in the distributionManagement site url.
50
<groupId>org.apache.maven.wagon</groupId>
51
<artifactId>wagon-scm</artifactId>
52
<version>${project.version}</version>
55
<groupId>org.apache.maven.scm</groupId>
56
<artifactId>maven-scm-manager-plexus</artifactId>
57
<version>${mavenScmVersion}</version>
60
<groupId>org.apache.maven.scm</groupId>
61
<artifactId>maven-scm-provider-svnexe</artifactId>
62
<version>${mavenScmVersion}</version>
66
<distributionManagement>
68
<id>my.svn.server</id>
69
<url>scm:svn:https://username@svn.apache.org/svn/root/module</url>
71
</distributionManagement>
75
Deploying your Maven site to CVS
77
Same as before, but changing svnexe to cvsexe and using a CVS svn url.
83
<groupId>org.apache.maven.wagon</groupId>
84
<artifactId>wagon-scm</artifactId>
85
<version>${project.version}</version>
88
<groupId>org.apache.maven.scm</groupId>
89
<artifactId>maven-scm-manager-plexus</artifactId>
90
<version>${mavenScmVersion}</version>
93
<groupId>org.apache.maven.scm</groupId>
94
<artifactId>maven-scm-provider-cvsexe</artifactId>
95
<version>${mavenScmVersion}</version>
99
<distributionManagement>
101
<id>my.cvs.server</id>
102
<url>scm:cvs:ext:username@cvs.apache.org:/cvs/root:module</url>
104
</distributionManagement>
108
Deploying your Maven site to GitHub's gh-pages
110
Same as before, but changing svnexe to gitexe and using a Git svn url.
116
<groupId>org.apache.maven.wagon</groupId>
117
<artifactId>wagon-scm</artifactId>
118
<version>${project.version}</version>
121
<groupId>org.apache.maven.scm</groupId>
122
<artifactId>maven-scm-manager-plexus</artifactId>
123
<version>${project.version}</version>
126
<groupId>org.apache.maven.scm</groupId>
127
<artifactId>maven-scm-provider-gitexe</artifactId>
128
<version>${project.version}</version>
132
<distributionManagement>
134
<id>my.git.server</id>
135
<url>scm:git:ssh://git@github.com/myuser/myproject.git</url>
137
</distributionManagement>
140
And in your settings.xml file:
144
<id>my.git.server</id>
145
<username>git</username>
146
<scmVersionType>branch</scmVersionType>
147
<scmVersion>gh-pages</scmVersion>
153
Using a Subversion based remote repository in Maven 2
158
Using a CVS based remote repository in Maven 2