[jira] [Commented] (CAMEL-4643) Make it easier to check outdated dependencies and avoid duplicate/different version definitions

["Christian Müller (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449100#comment-13449100 ] 

Christian Müller commented on CAMEL-4643:
-----------------------------------------

At present, we define version numbers of our dependencies in:
- pom.xml (only 3)
- parent/pom.xml
- platforms/karaf/features/pom.xml

We define our pluginManagement in:
- pom.xml
- parent/pom.xml

Wouldn't it be easier to define it only in parent/pom.xml?

Only the buildingstool module doesn't use org.apache.camel/camel-parent as parent (it's easy to change). Is there a reason for this?
                
> Make it easier to check outdated dependencies and avoid duplicate/different version definitions
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4643
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4643
>             Project: Camel
>          Issue Type: Task
>    Affects Versions: 2.8.2
>            Reporter: Christian Müller
>            Assignee: Christian Müller
>            Priority: Minor
>             Fix For: Future
>
>
> I want to put the version properties from platforms/karaf/features/pom.xml to parent/pom.xml to avoid duplicate/different version definitions.
> I want also add the bundle dependencies from our features file into a dependencyManagement section in platforms/karaf/features/pom.xml (or parent/pom.xml). With this it's much more easier to check the outdated dependencies.
> I will wait with this patch until Camel 2.9.0 is out to not to endanger the release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira