On Sun, 13 Dec 2015, Bob Paulin wrote:
So in short
Source in tika-parser
Dependencies managed in tika-parser and copied to module
Source in Modules
Dependencies managed in modules and consolidated via maven shade plugin.
Conflicting dependencies managed by maven.
IIRC there are some util /
> From: Bob Paulin
> Sent: December 13, 2015 7:34:03pm PST
> To: dev@tika.apache.org
> Subject: Tika 2.0 Source in Modules or tika-parser
>
> Hi,
>
> I've committed the first module break out to the tika 2.0 branch and I'd like
> to discuss the possibility of
Answers inline
On 12/14/2015 5:24 AM, Nick Burch wrote:
On Sun, 13 Dec 2015, Bob Paulin wrote:
So in short
Source in tika-parser
Dependencies managed in tika-parser and copied to module
Source in Modules
Dependencies managed in modules and consolidated via maven shade
plugin. Conflicting
the core jar?
-Original Message-
From: Bob Paulin [mailto:b...@bobpaulin.com]
Sent: Monday, December 14, 2015 9:16 AM
To: dev@tika.apache.org
Subject: Re: Tika 2.0 Source in Modules or tika-parser
Answers inline
On 12/14/2015 5:24 AM, Nick Burch wrote:
> On Sun, 13 Dec 2015, Bob Paul
I'd vote for a tiki-parser-common(s) artifact for common util classes and
dependencies.
> On Dec 14, 2015, at 10:54 AM, Ken Krugler <kkrugler_li...@transpac.com> wrote:
>
>
>> From: Bob Paulin
>> Sent: December 13, 2015 7:34:03pm PST
>> To: dev@tika.apach
On 14/12/15 16:26, Ray Gauss wrote:
I'd vote for a tiki-parser-common(s) artifact for common util classes and
dependencies.
That would make sense to me
Nick
On Mon, 14 Dec 2015, Bob Paulin wrote:
So there seems to be a pretty good consensus forming around moving the
sources but some differing opinions on where to put shared parser code.
I know it'll be a bit dull and some work, but... Could someone put
together a list (probably in the wiki or on
So there seems to be a pretty good consensus forming around moving the
sources but some differing opinions on where to put shared parser code.
tika-parser-commons-
Pros: We would be able to keep from adding another dependency to the
tika-core project.
Cons: All parsers would then require an
Hi,
I've committed the first module break out to the tika 2.0 branch and I'd
like to discuss the possibility of moving the source code from the
tika-parser projects to the modules. The implementation I committed is
based on the straw man version I proposed a few months ago which copies
the
