Interesting...I guess the size of our jar file is not an issue, but
separating them out would allow people not using the parser functionality to
avoid dependencies on all those parser jar files.
How would that have worked regarding directory structure and maven? Would
it look like this?:
tika
-- parsing
-- -- src
-- -- -- main
...
-- mime
-- -- src
-- -- -- main
...
-- encoding
-- -- src
-- -- -- main
...
... with a POM file in each of { parsing, mime, encoding }, and a parent POM
file in tika to coordinate building of all of them?
- Keith
Bertrand Delacretaz wrote:
>
> On 10/16/07, Keith R. Bennett <[EMAIL PROTECTED]> wrote:
>
>> ...Tika needs to do MIME type and encoding detection for the purpose of
>> parsing. I'd like to suggest elevating those services to be explicitly
>> stated services of Tika, so that we can increase Tika's usefulness to its
>> users...
>
> 100% agreed - I also suggested a while ago to make these separate
> Maven modules that build their own jars (so that people can use just
> those parts of Tika if they want), but IIRC people were against that.
>
--
View this message in context:
http://www.nabble.com/Exposing-MIME-Type-and-Encoding-Detection-tf4636584.html#a13254814
Sent from the Apache Tika - Development mailing list archive at Nabble.com.
