Yes, you can do it; see other answers.
However, popular wisdom is that it is a bad idea to use non-standard organizations for the Maven project, because (this is how the story happens), it tends to break Maven plugins (and other tools) that accept the standard organization. (At the very least, the tools are likely to be less thoroughly tested for non-standard organizations.)
Another problem is that people expect a standard project organization. Indeed, the “strong support” of a standard design organization is (IMO) one of Maven’s major retail outlets.
Can I make a radical proposal?
Instead of using a custom layout for your project due to CVS limitations, transfer the source code to a newer version control system, in which version history is stored in file and directory names.
This Wikipedia page is a good place to look for alternatives.
Stephen c
source share