Description of problem: The jbossnetwork, gatekeeper, sep, and slide-client projects do not share a common parent POM. There are things from the POMs that should be refactored into a common parent project such as, * dependency management section * plugin management section * build plugin configuration * reporting plugin configuration * common dependencies We should also reorganize projects into a one source tree so that it looks something like: csp | |----jbossnetwork | |----gatekeeper | |----sep | |----slide-client This way, someone can easily check out all of the projects, and then build(and even possibly deploy) them with a single command. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
A little more detail on projects and project structure. From the outset, I can see something like, csp | |----jbossnetwork | |----gatekeeper | |----sep | |----slide-client | |----build-tools | |----test-commons | |----csp-qa Some maven plugins, like those for checkstyle and pmd, expect to find their respective configuration files and other resources on the classpath. A recommended approach is to create something like a build-tools project that houses the resources. Then the projects that need them can declare the plugin dependencies. Any custom plugins that might be developed could also live under build-tools. test-commons would hold common unit test classes and resources that might be shared across projects. csp-qa would also hold common test resources, but primarily aimed at functional/acceptance tests like selenium.