You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Tyler Palsulich (JIRA)" <ji...@apache.org> on 2014/12/14 04:25:13 UTC

[jira] [Resolved] (TIKA-1384) Use tika-parent dependency management for common dependencies

     [ https://issues.apache.org/jira/browse/TIKA-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tyler Palsulich resolved TIKA-1384.
-----------------------------------
       Resolution: Done
    Fix Version/s:     (was: 1.8)
                   1.7

Final update in r1645379. There might be more duplicates hiding somewhere, but I don't see any.

> Use tika-parent dependency management for common dependencies
> -------------------------------------------------------------
>
>                 Key: TIKA-1384
>                 URL: https://issues.apache.org/jira/browse/TIKA-1384
>             Project: Tika
>          Issue Type: Improvement
>          Components: packaging
>            Reporter: Tyler Palsulich
>            Assignee: Tyler Palsulich
>            Priority: Minor
>             Fix For: 1.7
>
>
> If we list a dependency in the dependencyManagement section of the tika-parent pom.xml, we can then include that dependency in a child module without specifying a version.
> For example, I updated the junit dependencies yesterday: https://github.com/apache/tika/commit/2fec4c61267ed2c465e7411d50fbf7e9841523d5
> By using dependencyManagement, we can update the dependency version for all modules at once, rather than have different versions in different modules, like it was for junit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)