[jira] [Commented] (TIKA-3676) Consider making dl4j dependencies provided
[ https://issues.apache.org/jira/browse/TIKA-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17489597#comment-17489597 ] Nick Burch commented on TIKA-3676: -- As long as we provide sensible instructions on what to do, I'm happy to make this like our other "large bundle of native code" case for sqlite and require users to add the relevant pom entry for their platform / kitchen sink it themselves > 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)
[jira] [Commented] (TIKA-3676) Consider making dl4j dependencies provided
[ https://issues.apache.org/jira/browse/TIKA-3676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490903#comment-17490903 ] Hudson commented on TIKA-3676: -- SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #462 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/462/]) TIKA-3676 -- change tika-dl's dependencies to provided (tallison: [https://github.com/apache/tika/commit/cfbcaba59cc5d6edd4322459c8a6effc8c9544f2]) * (edit) tika-parsers/tika-parsers-ml/tika-dl/pom.xml * (edit) CHANGES.txt > 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 > Fix For: 2.3.1 > > > 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)