Apache Maven 3 Cookbook

Chapter 3
Subversion commands Mercurial commands Git commands
svn checkout
svn add
svn delete
svn commit
svn update
svn diff
svn log
svn merge
and so on.
Hg init
hg clone
hg add
hg commit
hg status
hg pull
hg push
hg serve
and so on.
git init
git clone
git add
git commit
git status
git diff
git reset
git merge
and so on.
The source code configuration (SCM) information can be added to the POM file of an Apache
Maven project.
...
...
...
...
...
The preceding code snippet shows details of a revision control repository added in a project
POM file. The connection and developerConnection elements represent the read-only
and read/write paths of the repository respectively. The tag element dictates which tag is
being worked upon, while the url field is an optional field for a publicly browseable view of
the source code.
How it works...
The workflow for the three revision control systems–SVN, Mercurial, and Git–can be different
depending on the configuration. However, a likely configuration for smaller teams (2-12
people) would involve a centralized repository even while you are leveraging benefits of
Distributed version control systems such as Git or Mercurial.
In such a case, the first step for a new developer would be to extract the source code on his
/ her workstation. With SVN, this would be the svn Checkout command, while for Git or
Mercurial you would use the clone command. In SVN, it is likely that you would be getting
only a copy of the HEAD revision while the clone command for Git / Mercurial extracts the
entire repository.
59