Bug 452507 - Refactor Maven Builds and Create Common Parent POM for Projects
Refactor Maven Builds and Create Common Parent POM for Projects
Status: CLOSED CURRENTRELEASE
Product: JBoss Customer Support Portal
Classification: Retired
Component: Other (Show other bugs)
1.3.9
All All
low Severity low
: ---
: ---
Assigned To: JBoss CSP Bug Watch List
:
Depends On:
Blocks: 454710
  Show dependency treegraph
 
Reported: 2008-06-23 09:58 EDT by John Sanda
Modified: 2008-08-21 10:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-20 14:27:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description John Sanda 2008-06-23 09:58:34 EDT
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:
Comment 1 John Sanda 2008-06-23 11:24:28 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.