oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OODT-89) Synchonize OODT-CAS components, which depend on one another, on a particular Apache-Tika version
Date Thu, 23 Dec 2010 02:55:00 GMT

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

Chris A. Mattmann updated OODT-89:
----------------------------------

    Component/s: push pull framework
                 metadata container
                 build proces
    Description: 
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

  was:

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


- classify

> 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
>          Components: build proces, metadata container, push pull framework
>    Affects Versions: 0.1-incubating
>         Environment: none
>            Reporter: Brian Foster
>            Assignee: Brian Foster
>            Priority: Minor
>             Fix For: 0.2
>
>         Attachments: OODT-89.2010-12-15.patch.txt
>
>
> 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.


Mime
View raw message