[
https://issues.apache.org/jira/browse/TIKA-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16041206#comment-16041206
]
Thomas Mortagne commented on TIKA-2368:
---------------------------------------
The source of the SentimentParser classes in sentiment-analysis-parser and
tika-parsers are very different so I'm not sure how this can be OK when you can
end up with one or the other pretty much randomly.
Which of those classes is the right one and is there any plan to actually fix
this issue ?
> Clean up SentimentParser dependencies
> -------------------------------------
>
> Key: TIKA-2368
> URL: https://issues.apache.org/jira/browse/TIKA-2368
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Minor
> Fix For: 1.15
>
>
> Is there any way to avoid reliance on edu.usc.ir's sentiment-analysis-parser?
> I ask because:
> {noformat}
> [WARNING] sentiment-analysis-parser-0.1.jar, tika-parsers-1.15-SNAPSHOT.jar
> define 1 overlapping classes:
> [WARNING] - org.apache.tika.parser.sentiment.analysis.SentimentParser
> [WARNING] tika-core-1.15-SNAPSHOT.jar, tika-translate-1.15-SNAPSHOT.jar
> define 4 overlapping classes:
> [WARNING] - org.apache.tika.language.translate.DefaultTranslator$1
> [WARNING] - org.apache.tika.language.translate.EmptyTranslator
> [WARNING] - org.apache.tika.language.translate.DefaultTranslator
> [WARNING] - org.apache.tika.language.translate.Translator
> {noformat}
> We should be ok keeping things as they are and excluding SentimentParser and
> tika-translate, but can we easily move the code that's still in edu.usc.ir's
> package into Tika?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
