If you are using Subversion as your favourite SCM for developing then you should take two minutes to read their best practices.

There you will see that:

The Subversion project officially recommends the idea of a “project root”, which represents an anchoring point for a project. A “project root” contains exactly three subdirectories: /trunk, /branches, and /tags. A repository may contain only one project root, or it may contain a number of them.

This is the most typical way of managing the tags and branches on Subversion. Jabox will not enforce you to follow the best practice, but if you let it, it will create the structure for you, and monitor your projects to see if the rule aplies to all of them.

When combining Subversion with Maven you need take into account the Maven SVN conventions.

There you will see that:

Before committing code to the Subversion repository we always set the svn:ignore property on the directory to prevent some files and directories to be checked in. We always exclude the IDE project files and the target/ directory.

Jabox will again avoid to enforce you, but by default give you the option to automatically prepare the svn:ignore property for you. This way the best practices will be followed and avoid you to step over their pitfalls in case you do otherwise.