To enable the use of the freshli CLI cache, the path to that cache needs to be provided as a global parameter, similar to how it is specified for the freshli executable. This location needs to be then provided to the dependency-history-maven project once it's support for caching to SQLite databases has been built (see corgibytes/dependency-history-maven#24). The caching support in dependency-history-maven will be configured to write to a table named AgentJavaHttpCache.
To enable the use of the
freshliCLI cache, the path to that cache needs to be provided as a global parameter, similar to how it is specified for thefreshliexecutable. This location needs to be then provided to thedependency-history-mavenproject once it's support for caching to SQLite databases has been built (see corgibytes/dependency-history-maven#24). The caching support independency-history-mavenwill be configured to write to a table namedAgentJavaHttpCache.