[
https://issues.apache.org/jira/browse/TIKA-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3676:
------------------------------
Description:
Dl4j dependencies are rather large. We can cut ~4-6 minutes off the build time
and prevent gigabytes transferring over various networks during the release
cycle (at least). With the recent upgrade to dl4j, the jar is now 1.4GB, up
from ~800MB in our 1.x branch.
We are currently packaging the kitchen-sink, e.g. every platform's native
libraries. For folks using our wrappers/parsers around dl4j, they can a)
easily include the dependencies that are "provided" or b) tailor their
dependencies for their OS/architecture.
What do you think?
was:
Dl4j dependencies are rather large. We can cut ~6 minutes off the build time
and prevent gigabytes transferring over various networks during the release
cycle (at least).
We are currently packaging the kitchen-sink, e.g. every platform's native
libraries. For folks using our wrappers/parsers around dl4j, they can a)
easily include the dependencies that are "provided" or b) tailor their
dependencies for their OS/architecture.
What do you think?
> Consider making dl4j dependencies provided
> ------------------------------------------
>
> Key: TIKA-3676
> URL: https://issues.apache.org/jira/browse/TIKA-3676
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> Dl4j dependencies are rather large. We can cut ~4-6 minutes off the build
> time and prevent gigabytes transferring over various networks during the
> release cycle (at least). With the recent upgrade to dl4j, the jar is now
> 1.4GB, up from ~800MB in our 1.x branch.
> We are currently packaging the kitchen-sink, e.g. every platform's native
> libraries. For folks using our wrappers/parsers around dl4j, they can a)
> easily include the dependencies that are "provided" or b) tailor their
> dependencies for their OS/architecture.
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
