[
https://issues.apache.org/jira/browse/TIKA-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102948#comment-18102948
]
Hudson commented on TIKA-4807:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk17 #1521 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1521/])
TIKA-4807: consolidate metadata registry regeneration into one script
(tallison:
[https://github.com/apache/tika/commit/2dc9f26ef26fe6177f5ac522655df6732d6af659])
* (edit)
tika-metadata-schema/src/test/java/org/apache/tika/metadata/schema/MetadataFieldTableTest.java
* (edit) .skills/metadata-schema.md
* (add) tika-metadata-schema/regen.sh
* (add) docs/modules/ROOT/pages/developers/metadata-keys.adoc
* (edit) docs/modules/ROOT/pages/developers/index.adoc
* (edit) docs/modules/ROOT/nav.adoc
* (edit)
tika-metadata-schema/src/test/java/org/apache/tika/metadata/schema/MetadataSchemaTest.java
* (edit) tika-metadata-schema/README.md
> 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)
