The service desk wrapper modules can not be the direct maven module of the Jeti Server as it would result in the Jeti Server as a pom maven project. It would mean the artefact result of the Jeti Server could be only pom file as generally a maven aggregate module.
The proposed structure is the following:
Email This Issue Base
Email This Issue Server
Service Desk Wrapper3
Service Desk Wrapper4
So the Base has 3 child modules and the Server depends on the wrappers.
build and packagaking success