My company uses multi-module projects. We have created a generic profile that will deploy our web applications for single-module deployments. However, we have to jump through a few hoops to deploy multi-module projects. The deployment configuration is looking for components that match:
<components>
                                <component>
                                    <name>${project.artifactId}</name>
                                    <artifact>${project.build.directory}/${project.build.finalName}.war</artifact>
                                </component>
                        </components>

except that the parent module does not have a build directory or a .war file. Is there a better way to achieve a generic deployment configuration with a multi-module project with this structure:

parent (pom - extends from global parent)
    child (jar)
    child2 (war)
    child3 (war)

In our case, the global parent pom file contains the configuration for the deployment. Is there a way to have deployment excluded if the project's packaging is anything but war/ear? Perhaps there is a better way to handle this than the way that we've implemented. Great work on the plugin, BTW. Get's us 90% of the way there.