zackster
05/27/2025, 8:26 AMcfsimplicity
05/27/2025, 4:21 PMzackster
05/28/2025, 9:55 AMcfsimplicity
05/28/2025, 10:16 AMtika-app.jar was self-contained. According to its MVN page, it has no "runtime" dependencies, only "compile" dependencies, which I take to mean everything it needs is baked into the jar. That's been my experience in practice. I've never had to download anything else other than tika-app.jar (55MB) to use it. Why does Lucee need to download 250MB+ of dependencies? Is that in case you want to run a Tika server or something? But then there's a different artifact tika-server-standard.jar for that.zackster
05/28/2025, 10:38 AMpom.xml
Lucee is different, in that it's automatically managing all this which usually works very nicely, just include the base artifact and everything required is downloaded and just works
Sure it's working for you without the dependencies, but I'm guessing with certain file types / operations, tika will crash out?
looking at the pom for https://mvnrepository.com/artifact/org.apache.tika/tika-app/3.2.0
maven lists these as compile dependencies, there's no scope in the pom.xml, so it defaults to both compile and runtime, so Lucee is recursively pulling em down
https://repo1.maven.org/maven2/org/apache/tika/tika-app/3.2.0/tika-app-3.2.0.pom
We could try something like adding a dependencies=boolean to mavenLoad()?
https://docs.lucee.org/reference/functions/mavenload.html
mavenLoad(input=['org.apache.tika:tika-app:3.2.0'], dependencies=false);
https://www.perplexity.ai/search/maven-compile-dependencies-IfVXvozvQ4mkDfDEt6zjCQcfsimplicity
05/28/2025, 1:08 PM