For 3.x, I think it might be. For 4.x, I think we should aim in that
direction. What do others think?
On Tue, Sep 24, 2024 at 12:33 PM Nicholas DiPiazza <
nicholas.dipia...@gmail.com> wrote:

> I feel like what I might want to do is remove pipes from Tika completely
> and create a second repository I've already done a lot of the work in my
> local workspace but I have a bunch more to go
>
> Does that sound like crazy talk?
>
> On Tue, Sep 24, 2024, 10:02 AM Tim Allison <talli...@apache.org> wrote:
>
> > @Nicholas DiPiazza <ndipia...@apache.org>
> > I don't think I'll have time to refactor tika-pipes out of tika-core
> before
> > the 3.x release. Is there an MVP we can do to get grpc working so that we
> > can release 3.x?
> >
> > All,
> >   Any blockers beyond the regression tests (and grpc)?
> >
> >       Best,
> >
> >               Tim
> >
> >
> > On Tue, Sep 24, 2024 at 9:30 AM Gary D. Gregory <ggreg...@apache.org>
> > wrote:
> >
> > > Hi All,
> > >
> > > Is there a time frame for 3.0.0? It looks like Apache CXF 4.1.0 depends
> > on
> > > 3.0.0 [1] and I'm waiting on CXF 4.1.0... Any guidance would be
> > > appreciated.
> > >
> > > TY!
> > > Gary
> > > [1] https://issues.apache.org/jira/browse/CXF-8671
> > >
> > > On 2024/08/21 17:08:22 Nicholas DiPiazza wrote:
> > > > I have a pull request for some class path loading fixes for Tika
> grpc.
> > > > Hoping to get that done today but it's a struggle so far
> > > >
> > > > On Wed, Aug 21, 2024, 11:30 AM Tim Allison <talli...@apache.org>
> > wrote:
> > > >
> > > > > All,
> > > > >
> > > > >   There are a couple of items documented on
> > > > > https://issues.apache.org/jira/browse/TIKA-4280 that we wanted to
> > take
> > > > > care
> > > > > of before the 3.0.0 release.
> > > > >
> > > > >   I can run a comparison btwn 2.x and 3.x on our regression corpus,
> > > and I
> > > > > can try to deal with javadocs.
> > > > >
> > > > >   Any recs on how to wrap up the other issues? Are there any other
> > > blockers
> > > > > not listed on that issue?
> > > > >
> > > > >   Thank you!
> > > > >
> > > > >            Best,
> > > > >
> > > > >                 Tim
> > > > >
> > > >
> > >
> >
>

Reply via email to