[
https://issues.apache.org/jira/browse/TIKA-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131650#comment-15131650
]
Bob Paulin commented on TIKA-1824:
----------------------------------
So before we go that way let me explain what about your previous suggestion
made me change my mind. Consider the developer looking at this in a lib
directory or an IDE. If they just see advanced-parser or cad-parser I feel
we're opening the door for confusion as there are many other libraries that do
parsing. Thought it's redundant to the maintainers to have tika-parser-* as a
prefix it could ease the life of the end user developer trying to sort out JAR
hell on there classpath.
Second I have the module suffix because I'm still mulling how to replace
tika-bundle. Currently there are still many tika dependencies that are not
OSGi friendly. We've been getting around this by embedding them in
tika-bundle. The module suffix jars do not have dependencies embedded so I was
considering creating projects with a bundle suffix that would embed the
dependencies individually as tika-bundle did. I'm curious what the rest of the
community thinks of this approach. Naturally if we figure out a way to
eliminate the need for 2 then I agree the module suffix is redundant and can be
removed. My 2 cents. Thanks so much for the feedback, these are great things
to be discussing.
> Tika 2.0 - Create Initial Parser Modules
> -----------------------------------------
>
> Key: TIKA-1824
> URL: https://issues.apache.org/jira/browse/TIKA-1824
> Project: Tika
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: Bob Paulin
> Assignee: Bob Paulin
>
> Create initial break down of parser modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
