I'm working on a project which has basically the same structure, however the fact that we have to add 3 projects or modules for each client and server and 2 others for the shared module seems a little too much for me. The convention in maven is to create a test folder parallel to the main folder both inside the src folder. Scouts creates packages immediately after the src so there are no main nor test folders and we have no option but to create many extra projects or to move all packages to the a new main folder. Maybe it would be convenient to modify scout's convention and add all new classes in a main folder. What do you think about this?
Scout uses Eclipse Tycho for building and testing (see ). Therefore you cannot use the default maven project structure. You need to create a new test fragment containing only the tests for your project.
There is a tutorial  and an example application . You can also check out the blog post .
In my opinion this is due to how dependencies are handled:
* Plain maven project:
Dependencies are defined in the pom.xml files, you can have different dependencies for the src/ and the test/ folder inside the same maven module.
* Maven Tycho project:
Dependencies are defined in the META-INF/MANIFEST.MF of the plugin (which is also a maven module). Even if you have 2 source folder src/ and test/ in your plugin, you can specify the dependencies only once.
If you follow this approach, this means that you will include testing dependencies into your productive code. This is not recommended.
I hope this helps.
Feel free to continue the discussion (here or on the tycho-user mailing list).