You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Brian Foster (JIRA)" <ji...@apache.org> on 2010/12/15 19:06:00 UTC
[jira] Created: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
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.
[jira] Updated: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ramirez updated OODT-89:
-----------------------------
Fix Version/s: (was: 0.2)
0.3
Updated dependencies to bring tika to 0.8 for all components and passed unit tests. Leaving this issue open as a reminder for when tika 0.9 is released as mentioned in the comment above.
> 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.3
>
> 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.
[jira] Commented: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "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=12976327#action_12976327 ]
Chris A. Mattmann commented on OODT-89:
---------------------------------------
I took care of some of this for the filemgr in OODT-58. I think all we have left is removing cas-pge and cas-crawler deps on Tika (probably not needed like Brian mentions). cas-product needs to be updated, and so does cas-curator too.
> 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.
[jira] Commented: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972279#action_12972279 ]
Brian Foster commented on OODT-89:
----------------------------------
- cas-pushpull added dependency to tika-parsers 0.8 in r1050215
> 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
>
> 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.
[jira] Updated: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ramirez updated OODT-89:
-----------------------------
Fix Version/s: (was: 0.3)
0.2
> 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.
[jira] Commented: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972189#action_12972189 ]
Brian Foster commented on OODT-89:
----------------------------------
- cas-metadata patch added r1050124
- cas-pge and cas-crawler (not sure why tika is listed . . . probably just a remove on the deps)
- cas-product depends on it . . . that probably needs a code patch
- currator has something in basic.xml: java -jar tika-app-0.5-SNAPSHOT.jar -m
> 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
>
> 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.
[jira] Commented: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "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=12971865#action_12971865 ]
Chris A. Mattmann commented on OODT-89:
---------------------------------------
+1! Please leave the issue open so we'll remember to upgrade to 0.9 when it comes out, thanks!
> 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
>
> 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.
[jira] Commented: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "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.
[jira] Updated: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Brian Foster (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Foster updated OODT-89:
-----------------------------
Attachment: OODT-89.2010-12-15.patch.txt
- attached patch for cas-metadata to be updated to use tika-core 0.8 . . . both pushpull and metadata can be updated to 0.9 when it is released
> 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
>
> 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.
[jira] Commented: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986096#action_12986096 ]
Paul Ramirez commented on OODT-89:
----------------------------------
Tika dependency is still present in the components below and should be removed as these are dependent on cas-metadata which is the only reason they had tika listed bogusly in the first place
cas-crawler
cas-pge
As for oodt-product that should remain the same for now as it depends on tika-0.2.
> 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.
[jira] Updated: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Paul Ramirez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Ramirez updated OODT-89:
-----------------------------
Fix Version/s: (was: 0.2)
0.3
Pushing off to 0.3 release.
> 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.3
>
> 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.
[jira] [Resolved] (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Brian Foster (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Foster resolved OODT-89.
------------------------------
Resolution: Fixed
Gonna resolve this issue and open a new one per 0.9 tika comments... this issue was completed... upgrading to 0.9 is another issue
> 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.4
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OODT-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris A. Mattmann updated OODT-89:
----------------------------------
Fix Version/s: (was: 0.3)
0.4
> 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.4
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OODT-89) Synchonize OODT-CAS components, which
depend on one another, on a particular Apache-Tika version
Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
[ 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.