[jira] Commented: (OODT-89) Synchonize OODT-CAS components, which depend on one another, on a particular Apache-Tika version

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971768#action_12971768 ] 

Chris A. Mattmann commented on OODT-89:
---------------------------------------

+1!

Let's standardize on the soon-to-be-coming Tika 0.9 release candidate. Should be here in a week or two. We could depend on 0.8, but I don't expect an OODT release (0.2) anytime in the next month or so, so we've got time to get the new 0.9 Tika release when it's rolled.

> Synchonize OODT-CAS components, which depend on one another, on a particular Apache-Tika version
> ------------------------------------------------------------------------------------------------
>
>                 Key: OODT-89
>                 URL: https://issues.apache.org/jira/browse/OODT-89
>             Project: OODT
>          Issue Type: Bug
>    Affects Versions: 0.1-incubating
>         Environment: none
>            Reporter: Brian Foster
>            Assignee: Brian Foster
>            Priority: Minor
>             Fix For: 0.2
>
>
> cas-metadata and cas-pushpull depend on 2 different versions of Apache Tika:
> *cas-metadata:*
> {noformat}
> [INFO] [dependency:tree]
> [INFO] org.apache.oodt:cas-metadata:jar:0.2-incubating
> ...
> [INFO] +- org.apache.tika:tika:jar:0.3:compile
> ...
> {noformat}
> *cas-pushpull:*
> {noformat}
> [INFO] [dependency:tree]
> [INFO] org.apache.oodt:cas-pushpull:jar:0.2-incubating
> ...
> [INFO] +- org.apache.oodt:cas-metadata:jar:0.2-incubating:compile
> [INFO] |  +- org.apache.oodt:pcs-input:jar:0.2-incubating:compile
> [INFO] |  +- org.apache.tika:tika:jar:0.3:compile
> ...
> [INFO] +- org.apache.tika:tika-core:jar:0.8:compile
> ...
> {noformat}
> When mvn package is run, the lib directory is populated with both: tika-0.3.jar and tika-core-0.8.jar
> - so what is happening is pushpull is really using tika-0.3.jar instead of tika-core-0.8.jar, since java classloader loads the first class it finds for the given classpath from the first jar it finds which is tika-0.3.jar since it ascii sorts before tika-core-0.8.jar

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.