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

Tim Allison resolved TIKA-4807.
-------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Would have preferred a better fix, but this is a bit better than it was?

I wanted the build to fail sooner, but I also don't want to run a single fast 
build every time we run ci/cd.

If anyone has better options, please open a new ticket.

> Improve metadata key registry usability for developers
> ------------------------------------------------------
>
>                 Key: TIKA-4807
>                 URL: https://issues.apache.org/jira/browse/TIKA-4807
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>             Fix For: 4.0.0
>
>
> We have a metadata key registry, which is great. However, now, when devs add 
> new keys they have to run a separate step to update the registry.
> This is less than ideal. Let's figure out how to make this easier/automate 
> this.
> Apologies [~dschmidt] 



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

Reply via email to