[ 
https://issues.apache.org/jira/browse/TIKA-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Allison updated TIKA-4316:
------------------------------
    Description: 
I proposed a tentative roadmap here: 
https://lists.apache.org/thread/9yfzf6qwpc7c6qnlp4tdwsdrnjvv7r1z

Let's use this ticket to discuss some high level changes in 4.x

Some thoughts:
1) Require Java 17
2) Remove tika-batch in favor of tika-pipes with filesystem dependencies
3) Move tika-pipes to a separate module. Consider moving non-trivial 
implementations of tika-pipes components to a separate project?
4) Remove unsupported dl4j and sentiment analysis modules and...? 
5) Avoid fat jars where possible -- at least move tika-server to a lib/* 
pattern with the assembly plugin instead of the shade plugin

  was:
I proposed a roadmap here: 
https://lists.apache.org/thread/9yfzf6qwpc7c6qnlp4tdwsdrnjvv7r1z

Let's use this ticket to discuss some high level changes in 4.x


> Goals for tika 4.x
> ------------------
>
>                 Key: TIKA-4316
>                 URL: https://issues.apache.org/jira/browse/TIKA-4316
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>
> I proposed a tentative roadmap here: 
> https://lists.apache.org/thread/9yfzf6qwpc7c6qnlp4tdwsdrnjvv7r1z
> Let's use this ticket to discuss some high level changes in 4.x
> Some thoughts:
> 1) Require Java 17
> 2) Remove tika-batch in favor of tika-pipes with filesystem dependencies
> 3) Move tika-pipes to a separate module. Consider moving non-trivial 
> implementations of tika-pipes components to a separate project?
> 4) Remove unsupported dl4j and sentiment analysis modules and...? 
> 5) Avoid fat jars where possible -- at least move tika-server to a lib/* 
> pattern with the assembly plugin instead of the shade plugin



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to