Maven Versioning Problems Having Different Purpose Modules Under One Parent
If you have modules with different purpose, you eventually hit the versioning problem.
When you change only one module and want to make a release, usually you go for parent project release, since otherwise there will be a mess having modules with different numbers. But another module was not changed! But the versioning number was increased.
Here is live example. You have a maven project. Then, you introduce an installer for it, which is also built with maven. You make this installer module a part of your application. But application installer and application itself serve for different purposes. When you fix a problem in the installer and release it, the versioning number of your application is also increased (if you go for the same versioning in the project).
The solution is simple. If you have modules which have different purposes, they should be contained in different parent projects. Or, as an alternavitve, if you are not afraid of different numbering of modules, you still can have different purpose modules under one parent.