Antmod's Subversion provider maps Antmod's concepts of modules, branches and tags onto Subversion using the recommended SVN repository layout. The following table illustrates how the mapping to a Subversion repository works:
| Antmod concept |
Subversion Provider mapping |
|---|---|
| Module | A top-level directory underneath the scm repository URL. |
| Trunk | Represented by the "module/trunk" directory in the Subversion repository. |
| Branch | A directory underneath the "module/branches/" directory in the Subversion repository. Each branch is a copy of the "module/trunk" directory in the Subversion repository. Example: "module/branches/1-5" |
| Tag | A directory underneath the "module/tags/" directory in the Subversion repository. Each tag is a copy of the "module/branches/x-y" directory in the Subversion repository. Example: "module/tags/1-5-3" |
The Subversion Provider transparently checks out the proper "module/trunk", "module/branches/x-y" or "module/tags/x-y-z" directory
onto the local disk in a normal "${antmod.checkoutdir}/release-ver/module/" directory. This way you do not notice the
difference between working with a CVS or a Subversion based module, and you can even mix them within one release.