[ 
https://issues.apache.org/jira/browse/TIKA-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17868724#comment-17868724
 ] 

Tim Allison edited comment on TIKA-4280 at 7/25/24 3:49 PM:
------------------------------------------------------------

Y, probably? I wasn't thinking of changing tika-server for 3.x just yet, but I 
thought we could start fresh with non-shaded jars with the tika-grpc server?

I'd hope for something similar to/as simple as this line: 
https://github.com/apache/tika-docker/blob/main/minimal/Dockerfile#L68 but know 
that .bat and .sh files get more complex shortly after the first proof of 
concept is developed. :D

What do you think?

One option for tika-server, is that we keep the fat jar, but that we also move 
to non-shaded jars in the service scripts and actually fix them so that they 
work.





was (Author: talli...@mitre.org):
Y, probably? I wasn't thinking of changing tika-server for 3.x just yet, but I 
thought we could start fresh with non-shaded jars with the tika-grpc server?

I'd hope for something similar to/as simple as this line: 
https://github.com/apache/tika-docker/blob/main/minimal/Dockerfile#L68 but know 
that .bat and .sh files get more complex shortly after the first proof of 
concept is developed. :D

What do you think?

One option for tika-server, is that we move to non-shaded jars in the service 
scripts and actually fix them so that they work.




> Tasks for the 3.0.0 release
> ---------------------------
>
>                 Key: TIKA-4280
>                 URL: https://issues.apache.org/jira/browse/TIKA-4280
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>
> I'm too lazy to open separate tickets. Please do so if desired.
> Some items:
> * Before releasing the real 3.0.0 we need to remove any "-M" dependencies
> * Decide about the ffmpeg issue and the hdf5 issue
> * Run the regression tests vs 2.9.x
> * Convert tika-grpc to use the dependency plugin instead of the shade plugin
> * Turn javadocs back on. I got errors during the deploy process because 
> javadoc needed the auto-generated code ("cannot find symbol 
> DeleteFetcherRequest"). We need to enable javadocs for the rest of the 
> project.
> Other things? Thank you [~tilman] for the first two!



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

Reply via email to