You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2020/03/11 15:13:00 UTC

[jira] [Commented] (TIKA-3068) Fix release configuration for tika-server as a service

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

Tim Allison commented on TIKA-3068:
-----------------------------------

The problem was that the assembly plugin was running after the shade plugin, which means that only the tika-server code (not the full uber jar with all dependencies) was being "assembled".  What took me some time to figure out was that maven was inheriting the order of plugins within the package phase from tika-parent, and the order in tika-server had no effect.

> Fix release configuration for tika-server as a service
> ------------------------------------------------------
>
>                 Key: TIKA-3068
>                 URL: https://issues.apache.org/jira/browse/TIKA-3068
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Blocker
>
> I just tried to roll rc1 for 1.24, and I found that the tika-server.jar was not included in the bin.tgz or bin.zip.
> We also need to include these artifacts in the deploy phase.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)