Bug 923458

Description of problem:

RHQ has no consistency on the location of versions for maven plugins and dependencies. Today every single possible variation allowed by maven can be found in poms. Having versions all over the place leads to duplication and sometimes use of the same dependency but with different version in submodules. 


The plan:
Update all the project poms to follow this pattern. Additionally, update all the dependencies to the latest version already in use by the project.

1) Properties with versions in root pom:
<jboss-jmx.version>4.2.3.GA</jboss-jmx.version>


2) Root pom will have dependencies with versions in dependencyManagement section:
<dependency>
 <groupId>jboss</groupId>
 <artifactId>jboss-jmx</artifactId>
  <version>${jboss-jmx.version}</version>
</dependency>


3) Root pom will have plugins with versions in pluginManagement section (build/pluginManagement):
<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>clirr-maven-plugin</artifactId>
  <version>${clirr.version}</version>
</plugin>


4) All submodules would use plugins and dependencies without version:
<dependency>
  <groupId>antlr</groupId>
  <artifactId>antlr</artifactId>
  <scope>provided</scope>
</dependency>

<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>clirr-maven-plugin</artifactId>
</plugin>


The versions to be extract in properties would be the full name of the dependency/plugin + version. For example: clirr-maven-plugin.version and not the current clirr.version.