Bug 923458 - Versioning for dependencies and plugins not consistent
Summary: Versioning for dependencies and plugins not consistent
Keywords:
Status: ON_DEV
Alias: None
Product: RHQ Project
Classification: Other
Component: No Component
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.7
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-19 21:56 UTC by Stefan Negrea
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Stefan Negrea 2013-03-19 21:56:54 UTC
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.


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