- Apache/
- Maven/
- Source Repository
- | Last Published: 2018-04-30
- | Get Sources
- Download
Source Repository
Maven projects use Git or Subversion to manage their source code: decisions to stay with Subversion or move to Git are tracked on Maven's Wiki.
Instructions on Subversion use can be found in the online book Version Control with Subversion. Instructions on Git use can be found in the online book Pro Git. Instructions for using the Apache Software Foundation Git repositories are at https://git-wip-us.apache.org.
Full Maven Sources
As described in the next paragraphs, Maven full source code is dispatched in more than 100 Git repos: Maven core, but also plugins or components, skins, a few svn2git read-only mirrors...
To check out full Maven source code easily, we provide a simple way using additional Google repo tool and an additional Git repository for tool's manifest:
| Apache Maven full source code | (GitHub mirror) |
- Install a git client if needed and the Google Repo tool.
- Check out a new repo workspace and prepare master branch:
repo init -u https://gitbox.apache.org/repos/asf/maven-sources.git repo sync repo start master --all
- In your IDE, import the projects you're interested in from the repo workspace. Or directly build with command line the component you want.
Maven Core
The Git repository for Maven contains a master branch which is the current development version. There is also a branch for maven-2.2.X or maven-3.0.x. In addition, the integration tests for the Maven core have their own repository.
| Apache Maven | (GitHub mirror) | |
| Apache Maven Core ITs | (GitHub mirror) |
Other Components
The source repositories for the various plugins are in Git, listed in the documentation of the respective plugin, reachable via the plugin index.
There are also many shared components and subsystems with their own source repositories, mainly in Git, some in Subversion.
Components in Git
The components in Git are:
Components in Subversion
Everything in Subversion can be checked-out from a single entry point, referencing each part through svn:externals
You can also check out every component separately. The components in Subversion are:
| the Maven site (this site) | (GitHub mirror) | |
| Maven Sandbox | (GitHub mirror) | |
| A variety of other subsystems (including obsolete trees replaced by git) |
Anonymous Access
Both subversion and git repositories may be cloned with either http or https. Only read-only access is available for http checkouts.
$ svn checkout http://svn.apache.org/repos/asf/maven/site/trunk
Developer Access
Everyone can access Subversion repositories via HTTP, but committers must checkout Subversion repositories via HTTPS to gain write access:
$ svn checkout https://svn.apache.org/repos/asf/maven/site/trunk
To commit changes to the repository, execute the following command to commit your changes (svn will prompt you for your password):
$ svn commit --username your-username -m "A message"
Access from behind a Firewall
For those users who are stuck behind a corporate firewall which is blocking HTTP access to the Subversion repository, you can try to access it via the developer connection:
$ svn checkout https://svn.apache.org/repos/asf/maven/site/trunk
Access through a Proxy
The Subversion client can go through a proxy, if you configure it to do so. First, edit your servers configuration file to indicate which proxy to use. The file's location depends on your operating system. On Linux or Unix it is located in the directory ~/.subversion. On Windows it is in %APPDATA%\Subversion (try echo %APPDATA%, note this is a hidden directory).
There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.
Example: Edit the servers file and add something like:
[global] http-proxy-host = your.proxy.name http-proxy-port = 3128