Aklakan commented on issue #2161:
URL: https://github.com/apache/jena/issues/2161#issuecomment-1913180619
Switching the cache to caffeine is doable, but unfortunately for my last
post I had only searched for 'guava'.
I noticed my code also relies on `com.google.common.collect.{Range,
RangeMap, RangeSet, etc}` for managing the ranges of cached data. This part
would be too much effort to replace - at least in the short run.
One way to resolve the dependent jars with maven could be done like this
(untested whether only including guava is sufficient):
```bash
# Fetch the serviceenhancer pom from maven central
mvn dependency:copy
-D'artifact=org.apache.jena:jena-serviceenhancer:4.10.0:pom' \
-Dmdep.stripVersion=true -D'outputDirectory=./target'
# Transitively retrieve dependencies by specific groupId(s)
# Output folder is relative to the given pom
mvn -f './target/jena-serviceenhancer.pom' \
dependency:copy-dependencies -Dtransitive
-D'includeGroupIds=com.google.guava' \
-DincludeScope=runtime -DoutputDirectory='.'
# Finally copy the downloaded jars to the fuseki extras folder
```
Using -D'excludeGroupIds=org.apache.jena' excludes the artifacts in that
group but still downloads their transitive dependencies :weary:
- Maybe for now its best to just update the documentation that guava is
needed in addition (possibly adding download links and/or the maven snippet)?
- Might packaging as a Fuseki module be an option that makes things easier?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
