[
https://issues.apache.org/jira/browse/TIKA-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271786#comment-14271786
]
Tim Allison commented on TIKA-1509:
-----------------------------------
First two questions:
1) This will probably require some big changes and will break compatibility.
When we complete this work, will that be Tika 2.0, whether or not we've
released 1.8 or 1.9 at the time? Or do we just want to raise all sorts of
flags and release it as the next 1.x?
2) How do we want to work on this? Some options:
a) Create a separate TIKA-1509 branch and merge to trunk when we're ready
for the major changes. This would require occasional merging from trunk to
keep TIKA-1509 fresh (not too bad).
b) Create a working 1.8 branch and do "breakable development for the next
generation" on trunk (as happens on Lucene/Solr). This would require
developers to make mods to 1.8 and trunk (I think?).
> Create configurable strategies for composite parsers
> ----------------------------------------------------
>
> Key: TIKA-1509
> URL: https://issues.apache.org/jira/browse/TIKA-1509
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
>
> Several parsers can handle the same mime type, and we are currently ordering
> which parser is chosen (roughly) by the alphabetic order of the parser class
> name.
> Let's allow users to configure strategies for picking parsers.
> ***NOTE: this description is just a place holder, will edit later.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
